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.
DescriptionJaroslav Spanko
2017-06-13 14:02:01 UTC
Description of problem:
On the direct cockpit instance on a server can see the CPU and memory usage of the docker containers
If I use a bridge connection to the host the CPU and memory usage is not filled
Version-Release number of selected component (if applicable):
cockpit-135-4.el7.x86_64
cockpit-docker-135-4.el7.x86_64
cockpit-system-135-4.el7.noarch
How reproducible:
100%
Steps to Reproduce:
1. use bridge connection to the docker tab
2. graphs are empty, also usage for containers
Actual results:
CPU and memory usage are empty
Expected results:
Graphs will be presented
Additional info:
Snaps in attachements
If by bridge you mean secondary server, then I am unable to reproduce. Are both servers running the same version of docker? Can you provide the OS and docker versions for the target. If you connect to the secondary server directly does the graph work then?
Hi Peter
Version are the same, RHEL 7.3 and docker 12.6-16
cockpit.x86_64 135-4.el7
cockpit-bridge.x86_64 135-4.el7
cockpit-dashboard.x86_64 135-4.el7
cockpit-doc.x86_64 135-4.el7
cockpit-docker.x86_64 135-4.el7
cockpit-kubernetes.x86_64 135-4.el7
cockpit-pcp.x86_64 135-4.el7
cockpit-storaged.noarch 135-4.el7
cockpit-system.noarch 135-4.el7
cockpit-ws.x86_64 135-4.el7
I attached the direct screen.
If you need any logs please let me know
Thx
Also just for note not only graphs but also CPU and memory usage in Containers content is not filled so i would say is not parse for some reason in this case.
Comment 9Ruben Romero Montes
2017-06-19 11:46:36 UTC
Closed as NOTABUG since upgrading to the latest release allows the graphs to be displayed properly.
cockpit-docker-138-6.el7.x86_64
cockpit-138-8.el7.x86_64
Description of problem: On the direct cockpit instance on a server can see the CPU and memory usage of the docker containers If I use a bridge connection to the host the CPU and memory usage is not filled Version-Release number of selected component (if applicable): cockpit-135-4.el7.x86_64 cockpit-docker-135-4.el7.x86_64 cockpit-system-135-4.el7.noarch How reproducible: 100% Steps to Reproduce: 1. use bridge connection to the docker tab 2. graphs are empty, also usage for containers Actual results: CPU and memory usage are empty Expected results: Graphs will be presented Additional info: Snaps in attachements