Bug 1442768

Summary:	Rhev inventory refresh fails after rhev upgrade from 3.6 to 4.0
Product:	Red Hat CloudForms Management Engine	Reporter:	Satoe Imaishi <simaishi>
Component:	Providers	Assignee:	Juan Hernández <juan.hernandez>
Status:	CLOSED ERRATA	QA Contact:	Ilanit Stein <istein>
Severity:	medium	Docs Contact:
Priority:	high
Version:	5.7.0	CC:	cpelland, jfrey, jhardy, jocarter, juan.hernandez, mgoldboi, obarenbo, oourfali, rspagnol, simaishi
Target Milestone:	GA	Keywords:	ZStream
Target Release:	5.8.0
Hardware:	All
OS:	All
Whiteboard:	rhev:ems_refresh
Fixed In Version:	5.8.0.10	Doc Type:	Bug Fix
Doc Text:	Previously when upgrading Red Hat Virtualization providers from versions 3.x to 4.x, CloudForms sometimes attempted to access the Red Hat Virtualization API at /api, which caused provider refresh failures. To avoid this issue, the API path has been updated in this CloudForms release to use /ovirt-engine/api instead of /api. As a result, CloudForms connects to Red Hat Virtualization 3.5 and newer providers successfully; however, Red Hat Virtualization 3.4 environments are no longer supported.	Story Points:	---
Clone Of:	1427653	Environment:
Last Closed:	2017-05-31 15:05:14 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	RHEVM	Target Upstream Version:
Embargoed:
Bug Depends On:	1427653
Bug Blocks:

Comment 3 Ilanit Stein 2017-05-11 11:57:21 UTC

Verified on CFME-5.8.0.14/RHV-3.6.8->4.0.7

rhevm.log contain only /ovirt-engine/api access. There is no /api access.

Steps:

Connect RHV-3.6 provider to CFME
Upgrade RHV to 4.0
On CFME UI the RHV provider credentails appeared as failed, and it was required to renew them, in order to be able to do a full refresh.

After that, full refresh worked just fine.

Comment 5 errata-xmlrpc 2017-05-31 15:05:14 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://access.redhat.com/errata/RHSA-2017:1367