Bug 1335561

Summary:	lvm versions higher than 2.02.150 cause systemd issues
Product:	[Community] LVM and device-mapper	Reporter:	Hussam Al-Tayeb <ht990332>
Component:	lvm2	Assignee:	LVM and device-mapper development team <lvm-team>
lvm2 sub component:	Default / Unclassified	QA Contact:	cluster-qe <cluster-qe>
Status:	CLOSED DUPLICATE	Docs Contact:
Severity:	unspecified
Priority:	unspecified	CC:	agk, heinzm, jbrassow, msnitzer, prajnoha, zkabelac
Version:	2.02.153	Flags:	rule-engine: lvm-technical-solution? rule-engine: lvm-test-coverage?
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2016-05-16 08:49:52 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 Hussam Al-Tayeb 2016-05-12 13:51:47 UTC

if I do systemctl daemon-reexec, there are zombie systemd-gpt something and other systemd-something processes. They stay there for a whole minute and block bus connections in the meantime.

This started happening after 2.02.151 lvm update.
The last version that did not cause this was 2.02.150

This is mostly an annoyance since the zombie processes do disappear after a minute and "systemctl something" operations start working again.
However in that whole minute, I get errors connecting to bus if I "systemctl start something".

Comment 1 Hussam Al-Tayeb 2016-05-12 14:34:23 UTC

The only non-zombie systemd generator process was the lvm one. so it appears to have been stuck for a minute or so.

Comment 2 Peter Rajnoha 2016-05-16 08:07:03 UTC

This is also reported as bug #1334063 (for Fedora rawhide).

Comment 3 Hussam Al-Tayeb 2016-05-16 08:49:52 UTC

Ok, thank you. I will mark it as duplicate since that one was reported earlier :)

*** This bug has been marked as a duplicate of bug 1334063 ***