Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Description of problem:
pminfo fetch fails to display the container information.
Version-Release number of selected component (if applicable):
Red Hat Enterprise Linux 7.2
pcp-3.10.6-2.el7.x86_64
How reproducible:
Always
Steps to Reproduce:
1. install upstream docker-1.10+ and start the docker daemon.
2.instantiate a container by an image from a known repository.
3. start PMCD and enable pmdaroot for enabling container information collection.
Actual results:
# pminfo -f containers.name
containers.name
No value(s) available!
Expected results:
Execution of pminfo --fetch command should yield result.
#pminfo -f containers.name
containers.name
inst [9 or "a2629e987421cd135b4d710104629578b7c61026762d8e07a486c408a288fb56"] value "TEST2"
Additional info:
pcp looks for /var/lib/containers/<container id>/config.json by default but from docker 1.10+ the configuration has changed to config.v2.json.
https://github.com/performancecopilot/pcp/commit/a1e2cae3a4d05fab522fef2207778be52ac76054
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://rhn.redhat.com/errata/RHBA-2016-2344.html
Description of problem: pminfo fetch fails to display the container information. Version-Release number of selected component (if applicable): Red Hat Enterprise Linux 7.2 pcp-3.10.6-2.el7.x86_64 How reproducible: Always Steps to Reproduce: 1. install upstream docker-1.10+ and start the docker daemon. 2.instantiate a container by an image from a known repository. 3. start PMCD and enable pmdaroot for enabling container information collection. Actual results: # pminfo -f containers.name containers.name No value(s) available! Expected results: Execution of pminfo --fetch command should yield result. #pminfo -f containers.name containers.name inst [9 or "a2629e987421cd135b4d710104629578b7c61026762d8e07a486c408a288fb56"] value "TEST2" Additional info: pcp looks for /var/lib/containers/<container id>/config.json by default but from docker 1.10+ the configuration has changed to config.v2.json. https://github.com/performancecopilot/pcp/commit/a1e2cae3a4d05fab522fef2207778be52ac76054