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:
Wrong VM state get for vms in ovirt4.0

Version-Release number of selected component (if applicable):
libgovirt-0.3.3-2.el7.x86_64
virt-viewer-2.0-8.el7.x86_64

How reproducible:
100%

Steps to Reproduce:
1. Prepare a running vm in ovirt 4.0.
2. Got the ca file from ovirt 4.0.
$ wget -O 2.crt http://ibm-x3250m5-03.rhts.eng.pek2.redhat.com/ovirt-engine/services/pki-resource?resource=ca-certificate&format=X509-PEM-CA
3. Connect the vm by remote-viewer with ovirt uri.
$ remote-viewer --ovirt-ca-file=2.crt ovirt://ibm-x3250m5-03.rhts.eng.pek2.redhat.com/$your_vm

Actual results:
An error dialog with info "Couldn't open oVirt session: oVirt VM xiaodwan-test is not running" pops up.

Expected results:
remote-viewer should open the vm correctly.

Additional info:

The difference of rest api between 4.0 and 3.6:
for 4.0,   <status>up</status>
for 3.6, <status><state>up</state></status>

The changes are documented in https://github.com/oVirt/ovirt-engine/tree/master/backend/manager/modules/restapi

Created attachment 1167842 [details]
rest api debug for ovirt 4.0

For now we can go with this upstream fix https://git.gnome.org/browse/libgovirt/commit/?id=948ce7168efa7c1fca5f1f6390f94191d709590b
More work will be needed for proper support of the new API.

We'll need to get this in 7.2.z too.

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-2229.html