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.

Bug 1813858

Summary: libgovirt needs to be refactored for using SDK v4
Product: Red Hat Enterprise Linux 8 Reporter: Steven Rosenberg <srosenbe>
Component: libgovirtAssignee: Eduardo Lima (Etrunko) <elima>
Status: CLOSED DUPLICATE QA Contact: SPICE QE bug list <spice-qe-bugs>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 8.4   
Target Milestone: rc   
Target Release: 8.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2020-03-16 13:20:46 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:
Embargoed:
Bug Depends On:    
Bug Blocks: 1785615    
Attachments:
Description Flags
Screen Shot of Error when choosing Change CD none

Description Steven Rosenberg 2020-03-16 10:18:35 UTC
Description of problem: When running a VM in ovirt engine and choosing Change CD on the Remote Viewer, the dialog displays “Method Not Allowed” instead of the list of iso files while the engine logs print [1]. This message is produced because the http GET /ovirt-engine/api message’s version in the header is 3 instead of 4.


Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1. Run a VM within ovirt engine
2. Choose Console in order to run the Remote Viewer
3. In the Remote Viewer menu, choose File -> Change CD

Actual results:

The Remote Viewer Dialog displays the message “Method Not Allowed” and the engine prints the warning [1].

Expected results:

The Remote Viewer would display the list of iso files from the iso repository.

Additional info:

[1] 2020-03-15 13:46:42,918+02 WARN  [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (default task-6) [7c6f1298] EVENT_ID: DEPRECATED_API(13,000), Client from address "0:0:0:0:0:0:0:1" is using version 3 of the API, which has been deprecated since version 4.0 of the engine, and will no longer be supported starting with version 4.3. It is highly recommended to update the client to use a supported version of the API and the SDKs, before upgrading to version 4.3 of the engine.

Comment 1 Steven Rosenberg 2020-03-16 10:24:14 UTC
Created attachment 1670498 [details]
Screen Shot of Error when choosing Change CD

Comment 2 Eduardo Lima (Etrunko) 2020-03-16 13:20:46 UTC

*** This bug has been marked as a duplicate of bug 1801226 ***