Bug 1272082

Summary:	Can't record archives without pmcd with Python PMAPI pmgui
Product:	[Fedora] Fedora	Reporter:	Marko Myllynen <myllynen>
Component:	pcp	Assignee:	Nathan Scott <nathans>
Status:	CLOSED EOL	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	23	CC:	brolley, fche, lberk, mgoodwin, nathans, pcp, scox
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-12-20 14:59:58 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 Marko Myllynen 2015-10-15 12:47:15 UTC

Description of problem:
This one is firmly in the nice-to-have category.

pmlogger(1) can collect metrics without pmcd(1) using local DSO PMDAs with the -o option. PCPIntro(1) states that @ as host has a special meaning, it refers to PM_CONTEXT_LOCAL. However, when using pmgui.pmRecordAddHost, @ is used with the -h option and pmlogger fails to start. Since adding -h is currently hard-coded it's not possible, for example, to workaround this by adding -o with pmgui.pmRecordControl/PM_REC_SETARGS. So it would be nice to pass "-o" instead of "-h @" to pmlogger when the host is @.

For the above to be fully usable, it should probably be possible to pass -K <spec> via the API as well. While PM_REC_SETARGS already should allow this, a Python client started with -K can't query its own parameters for -K so something like pmapi.pmGetOptionSpecLocal() would probably be needed.

I'm not entirely sure would this be worth the effort but let's at least document the current situation here, just for the record.

Comment 1 Marko Myllynen 2015-12-09 16:01:28 UTC

This limitation concerns only the pmgui approach, pmi can be used instead to create archives with -L.

Comment 2 Fedora End Of Life 2016-11-24 12:47:44 UTC

This message is a reminder that Fedora 23 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 23. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora  'version'
of '23'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 23 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 3 Fedora End Of Life 2016-12-20 14:59:58 UTC

Fedora 23 changed to end-of-life (EOL) status on 2016-12-20. Fedora 23 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.