Bug 1338518 - docker tab doesn't show running images
Summary: docker tab doesn't show running images
Keywords:
Status: CLOSED DUPLICATE of bug 1338512
Alias: None
Product: ovirt-engine
Classification: oVirt
Component: Backend.Core
Version: 4.0.0
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: ovirt-4.0.0-rc
: ---
Assignee: Vinzenz Feenstra [evilissimo]
QA Contact: Aharon Canan
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-05-22 12:00 UTC by Sandro Bonazzola
Modified: 2016-05-23 08:26 UTC (History)
3 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2016-05-23 07:12:22 UTC
oVirt Team: Virt
Embargoed:
michal.skrivanek: ovirt-4.0.0?
rule-engine: planning_ack?
michal.skrivanek: devel_ack+
rule-engine: testing_ack?

Attachments (Terms of Use)

Description Sandro Bonazzola 2016-05-22 12:00:08 UTC 
Installed guest agent within a VM, running "docker run cirros" within it.

I've checked the host and vdsm is reading guest agent data showing cirros image running within the vm but the engine is not showing it in the docker tab of the vm.

ovirt-engine-4.0.0-0.0.master.20160521171336.git2e1899b.el7.centos.noarch
Comment 1 Vinzenz Feenstra [evilissimo] 2016-05-23 07:12:22 UTC 
Caused by the exception you have found in BZ#1338512 = That makes the guest agent stop report anything

*** This bug has been marked as a duplicate of bug 1338512 ***
Comment 2 Sandro Bonazzola 2016-05-23 07:45:58 UTC 
(In reply to Vinzenz Feenstra [evilissimo] from comment #1)
> Caused by the exception you have found in BZ#1338512 = That makes the guest
> agent stop report anything
> 
> *** This bug has been marked as a duplicate of bug 1338512 ***

Are you sure?
I workarounded the exception there by commenting the wrong line and returning ["",""] and as I said, vdsm now is reading agent data.
So it seems an issue between vdsm and the engine.
Comment 3 Vinzenz Feenstra [evilissimo] 2016-05-23 08:26:03 UTC 
After investigating in the affected environment, the issue of no reports is really caused by the same issue.

Keeping it closed.

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