Bug 1277447

Summary:	libgovirt needs to access /ovirt-engine/api/ rather than /api/
Product:	Red Hat Enterprise Linux 6	Reporter:	Christophe Fergeau <cfergeau>
Component:	libgovirt	Assignee:	Christophe Fergeau <cfergeau>
Status:	CLOSED ERRATA	QA Contact:	SPICE QE bug list <spice-qe-bugs>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	6.7	CC:	djasa, jkurik, tjelinek, tpelka
Target Milestone:	rc	Keywords:	ZStream
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	libgovirt-0.3.2-2.el6	Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:
Clones:	1297810 (view as bug list)		Environment:
Last Closed:	2016-05-10 21:18:54 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:	1200067, 1297810

Description Christophe Fergeau 2015-11-03 10:52:41 UTC

When opening a .vv file from a RHEV 3.6+ instance, the .vv file should have an [ovirt] section with several items including a jsessionid cookie to use to authenticate with the instance. However, as described in https://bugzilla.redhat.com/show_bug.cgi?id=1276083#c3 , the jsessionid cookie to use is different for /ovirt-engine/api and /api. The jsessionid value in the .vv file is meant for /ovirt-engine/api, but RHEL6 libgovirt tries to use /api, which means authentication to the REST API is not going to work in this scenario (RHEL6 client).

Changing libgovirt so that it uses /ovirt-engine/api (as in RHEL7) seems to be the easiest/cleanest way of fixing that. Other options involve adding more fields to the .vv file.

Comment 2 Christophe Fergeau 2015-12-08 09:44:07 UTC

(In reply to Christophe Fergeau from comment #0)
> Changing libgovirt so that it uses /ovirt-engine/api (as in RHEL7) 

Moving to POST as this is already done upstream.

Comment 8 errata-xmlrpc 2016-05-10 21:18:54 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-0832.html