Bug 1327737

Summary: pcp does not show container info for docker 1.10 and above
Product: Red Hat Enterprise Linux 7 Reporter: Deepu K S <dkochuka>
Component: pcpAssignee: Nathan Scott <nathans>
Status: CLOSED ERRATA QA Contact: Miloš Prchlík <mprchlik>
Severity: low Docs Contact:
Priority: unspecified    
Version: 7.2CC: brolley, dkochuka, fche, lberk, mbenitez, mgoodwin, mprchlik, nathans
Target Milestone: rc   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: pcp-3.11.2-4.el7 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-11-04 04:23:17 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 Deepu K S 2016-04-15 18:55:23 UTC
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

Comment 4 Miloš Prchlík 2016-08-20 15:24:24 UTC
Verified for build pcp-3.11.3-3.el7.

Comment 6 errata-xmlrpc 2016-11-04 04:23:17 UTC
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