Bug 1302139

Summary:	VM permanently tries to read /dev/shm/lttng-ust-wait-5 saturating logs.
Product:	[Red Hat Storage] Red Hat Ceph Storage	Reporter:	Mike Hackett <mhackett>
Component:	Unclassified	Assignee:	Brad Hubbard <bhubbard>
Status:	CLOSED ERRATA	QA Contact:	ceph-qe-bugs <ceph-qe-bugs>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	1.3.1	CC:	bhubbard, branto, jdurgin, kdreyer, mlawrenc, tganguly, vakulkar
Target Milestone:	rc	Keywords:	CodeChange, Patch
Target Release:	1.3.2
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:	RHEL: ceph-0.94.5-8.el7cp Ubuntu: ceph_0.94.5-5redhat1trusty	Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2016-02-29 14:45:14 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Mike Hackett 2016-01-26 22:13:09 UTC

Description of problem:

Ubuntu 14.04
Ceph 94.5-1trusty - But liblttng is also packaged in RHCS 1.3.1 so downstream is susceptible to this as well.
liblttng-ust0
libvert
Bug is open with Canonical: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1432644/

Logs are constantly spammed with:
[4220163.899438] type=1400 audit(1447230173.207:7763726): apparmor="DENIED" operation="open" profile="libvirt-" name="/run/shm/lttng-ust-wait-5" pid=69948 comm="qemu-system-x86" requested_mask="r" denied_mask="r" fsuid=111 ouid=0

VM permanently tries to read /dev/shm/lttng-ust-wait-5

When used with enforced apparmor profile, this results in logs filled with denied messages.
As I understand it, liblttng is here to allow tracing / debugging in python (not sure). Maybe virt-manager shouldn't be shipped with debugging mode enabled by default, or maybe it is a perfectly legitimate feature and the apparmor profile should be updated.

lttng is disabled in Infernalis by default, but need to address issue being seen in Hammer.

Upstream bug ID: http://tracker.ceph.com/issues/14520

Comment 2 Josh Durgin 2016-01-26 22:29:48 UTC

Upstream ceph commits 5d204db..a81bcf7 (in the hammer branch) fix this.

Comment 3 Brad Hubbard 2016-02-03 05:38:28 UTC

Josh, Is a81bcf7 relevant to this bug?

Comment 4 Josh Durgin 2016-02-03 05:57:29 UTC

(In reply to Brad Hubbard from comment #3)
> Josh, Is a81bcf7 relevant to this bug?

Yes, it's needed since d02beff1cf7650fe6e57cdafe64dcbee2631ed52 introduces the Singleton that it fixes.

Comment 5 Brad Hubbard 2016-02-03 06:05:20 UTC

My bad, sorry Josh.

Comment 6 Boris Ranto 2016-02-03 23:02:34 UTC

You will probably need to back-port only the following patch:

https://github.com/dillaman/ceph/commit/e53d66e42b1c3aea47832f7e8983284ec45d9efa

The rest of the upstream PR should already be covered by bz 1304455.

Comment 14 monti lawrence 2016-02-17 18:51:05 UTC

Moving to VERIFIED per kdreyer in 2/17 PM call.

Comment 16 errata-xmlrpc 2016-02-29 14:45:14 UTC

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2016:0313