Bug 1327757

Summary:	service pmie stop interferes with pmmgr pmie instances
Product:	[Fedora] Fedora	Reporter:	Frank Ch. Eigler <fche>
Component:	pcp	Assignee:	pcp-maint <pcp-maint>
Status:	CLOSED WONTFIX	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	rawhide	CC:	fche, lberk, mgoodwin, nathans, pcp
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:	2019-03-05 03:37:36 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:

Description Frank Ch. Eigler 2016-04-15 21:05:11 UTC

service pmie should be completely independent of pmmgr-managed pmie.
A bug probably somewhere in the rc.d pmie control scripts messes things up.
100% reproducible under 3.11.1 and git pcp.

To reproduce:

# yum install pmmgr
# chkconfi gpmmgr on
# service pmmgr start
[wait a couple of seconds]
# chkconfig pmie on
# service pmie start
# pcp
[observe a copy of pmie run from service* and at least one under pmmgr]
# service pmie stop
[this may fail; pmie sometimes blocks signals, which is a separate bug]
# pcp
[observe all copies of pmie are no longer represented]
# ps awux | grep pmie
[observe pmmgr-managed pmie instances are still running]
# ls -l /var/lib/pcp/tmp/pmie
[observe empty]

Comment 1 Nathan Scott 2019-03-05 03:37:36 UTC

This issue is not going to be addressed by PCP maintainers with limited resources, and is an unlikely combination in practice anyway (~noone uses pmmgr, and even fewer use both the pmmgr service and the pmie service simultaneously).