Bug 1348186 - Suboptimal error messages with --container
Summary: Suboptimal error messages with --container
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Fedora
Classification: Fedora
Component: pcp
Version: 27
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: pcp-maint
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-06-20 11:40 UTC by Marko Myllynen
Modified: 2018-11-28 14:19 UTC (History)
6 users (show)

See Also:
Fixed In Version:
Clone Of:
Environment:
Last Closed: 2018-11-28 14:19:12 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Marko Myllynen 2016-06-20 11:40:27 UTC
Description of problem:
pmval --container wrong <metric> or pmval --container <ambiguous> <metric> both print out:

pmval: pmGetInDom(60.3): Bad file descriptor

Which is probably technically correct but not very user-friendly.

In case there is only one container running, say abcdefg, then --container ab still works but --container a fails with the above error, this is perhaps expected.

Comment 1 Fedora End Of Life 2017-07-25 21:08:13 UTC
This message is a reminder that Fedora 24 is nearing its end of life.
Approximately 2 (two) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 24. 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 '24'.

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 24 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 2 Jan Kurik 2017-08-15 09:03:24 UTC
This bug appears to have been reported against 'rawhide' during the Fedora 27 development cycle.
Changing version to '27'.

Comment 3 Ben Cotton 2018-11-27 13:29:57 UTC
This message is a reminder that Fedora 27 is nearing its end of life.
On 2018-Nov-30  Fedora will stop maintaining and issuing updates for
Fedora 27. 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 '27'.

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 27 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 4 Lukas Berk 2018-11-27 15:05:32 UTC
Hi Marko,

With latest pcp I see:

% pmval --container wrong hinv.ncpu

metric:    hinv.ncpu
host:      HOST
semantics: discrete instantaneous value
units:     none
samples:   all

pmval: pmFetch: Container not found
pmval: pmFetch: Container not found
[...]

Do you consider this sufficient to close the bug?  Or should we reassign to Rawhide?

Comment 5 Marko Myllynen 2018-11-28 06:41:56 UTC
Yes, looks good (didn't check the ambiguous case but assuming it's improved as well). Thanks!


Note You need to log in before you can comment on or make changes to this bug.