Fixed here: https://github.com/ceph/teuthology/pull/852 This was my fault. I'm adding pcp to our test infrastructure, and didn't anticipate (or reveal in my testing) that there would be selinux denials coming from it. On Mon, May 2, 2016 at 1:03 AM, Boris Ranto <branto@xxxxxxxxxx> wrote: > On Sat, 2016-04-30 at 21:32 -0400, Sage Weil wrote: >> Hi Boris, >> >> Do you know why these selinux failures are happening on the jewel >> branch? >> I don't see any obvious differences from master, which doesn't seem >> to be >> hitting these. >> >> http://pulpito.ceph.com/sage-2016-04-30_16:27:00-rados-jewel---basic- >> smithi/159724 >> >> Thanks! >> sage >> > > Hi Sage, > > all of these are related to PCP (Performance Co-Pilot), not Ceph > directly. You can notice that source context (scontext) is always > > pcp_pmlogger_t (or pcp_pmcd_t in one occurrence) > > which refers to pmlogger (or pmcd daemon). > > Maybe, someone have set-up PCP to measure performance of Ceph clusters? > I can't say much more as I'm not familiar with PCP. AFAIK, PCP is not a > dependency of Ceph so removing it should also make the denials > disappear. > > -boris > > -- > To unsubscribe from this list: send the line "unsubscribe ceph-devel" in > the body of a message to majordomo@xxxxxxxxxxxxxxx > More majordomo info at http://vger.kernel.org/majordomo-info.html -- To unsubscribe from this list: send the line "unsubscribe ceph-devel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
