From: John Spray <jspray@redhat.com>
To: 严正 <zyan@redhat.com>, "Ilya Dryomov" <idryomov@redhat.com>
Cc: ceph-devel <ceph-devel@vger.kernel.org>
Subject: Re: teuthology SELinux failures
Date: Tue, 6 Jun 2017 14:26:29 +0100 [thread overview]
Message-ID: <CALe9h7fpmcZ6BwEA8=gZAa-MGNm8COotvdPMrokLk0Ah__RDnA@mail.gmail.com> (raw)
In-Reply-To: <CALe9h7fuiqMFTsEPaLa1uSpBnVj2L8M=dacAVy0ZMiAE+Uzs9w@mail.gmail.com>
Adding Ilya and Zheng -- do you guys happen to know what might have
changed in the current testing kernel to start seeing all these
selinux issues? I'm still seeing it in my latest runs.
Here's a recent example:
http://qa-proxy.ceph.com/teuthology/jspray-2017-06-05_15:00:03-multimds-wip-jcsp-testing-20170604-testing-basic-smithi/1260536/teuthology.log
John
On Wed, May 31, 2017 at 10:12 PM, John Spray <jspray@redhat.com> wrote:
> On Wed, May 31, 2017 at 9:23 PM, Yehuda Sadeh-Weinraub
> <yehuda@redhat.com> wrote:
>> We started seeing SELinux related failures in recent teuthology run, e.g.:
>> http://pulpito.ceph.com/yehudasa-2017-05-30_14:55:10-rgw-wip-rgw-mdsearch---basic-smithi/
>>
>> It seems that it's unrelated to the runs themselves, possibly postfix
>> that's running in the background is triggering these. Any idea what we
>> should do there?
>
> My assumption had been that the new failures were from a kernel
> change, because I had two runs overnight, one with "-k distro" and one
> with "-k testing", and it was only the testing one that had the masses
> of selinux failure.
>
> Possibly these rgw jobs did not have a -k flag and therefore ended up
> with the testing kernel that had been installed with previous jobs.
>
> I have no insight about the nature of the selinux breakage itself though!
>
> John
>
>>
>> Yehuda
>> --
>> To unsubscribe from this list: send the line "unsubscribe ceph-devel" in
>> the body of a message to majordomo@vger.kernel.org
>> More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2017-06-06 13:26 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-31 20:23 teuthology SELinux failures Yehuda Sadeh-Weinraub
2017-05-31 21:12 ` John Spray
2017-06-06 13:26 ` John Spray [this message]
2017-06-06 13:55 ` Ilya Dryomov
2017-06-06 16:42 ` Vasu Kulkarni
2017-06-01 15:33 ` Boris Ranto
2017-06-01 16:15 ` Vasu Kulkarni
2017-06-01 16:39 ` John Spray
2017-06-01 16:50 ` Yuri Weinstein
2017-06-02 2:44 ` Nathan Cutler
2017-06-02 15:31 ` Yuri Weinstein
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CALe9h7fpmcZ6BwEA8=gZAa-MGNm8COotvdPMrokLk0Ah__RDnA@mail.gmail.com' \
--to=jspray@redhat.com \
--cc=ceph-devel@vger.kernel.org \
--cc=idryomov@redhat.com \
--cc=zyan@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.