Bug 1442769 – Rhev inventory refresh fails after rhev upgrade from 3.6 to 4.0

Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.

Bug 1442769 - Rhev inventory refresh fails after rhev upgrade from 3.6 to 4.0

Summary:	Rhev inventory refresh fails after rhev upgrade from 3.6 to 4.0

Status:	CLOSED ERRATA

Aliases:	None

Product:	Red Hat CloudForms Management Engine
Classification:	Red Hat
Component:	Providers (Show other bugs)
Sub Component:
Version:	5.7.0
Hardware:	All All

Priority	high Severity medium
Target Milestone:	GA
Target Release:	5.7.3
Assigned To:	Juan Hernández
QA Contact:	Ilanit Stein
Docs Contact:

URL:
Whiteboard:	rhev:ems_refresh
Keywords:	ZStream

Depends On:	1427653
Blocks:
	Show dependency tree / graph

Reported:	2017-04-17 09:02 EDT by Satoe Imaishi
Modified:	2017-06-28 10:59 EDT (History)
CC List:	10 users (show)

See Also:
Fixed In Version:	5.7.3.1
Doc Type:	If docs needed, set a value
Doc Text:
Story Points:	---
Clone Of:	1427653
Environment:
Last Closed:	2017-06-28 10:59:55 EDT
Type:	---
Regression:	---
Mount Type:	---
Documentation:	---
CRM:
Verified Versions:
Category:	---
oVirt Team:	---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	RHEVM

Attachments	(Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

External Trackers
Tracker	ID	Priority	Status	Summary	Last Updated
Red Hat Product Errata	RHSA-2017:1601	normal	SHIPPED_LIVE	Important: CFME 5.7.3 security, bug fix and enhancement update	2017-06-28 14:51:52 EDT

Groups: None (edit)

Comment 2 Oved Ourfali 2017-04-30 08:33:41 EDT

Moving to POST, as the PR is backported.

Comment 3 Satoe Imaishi 2017-06-06 16:28:56 EDT

PR: https://github.com/ManageIQ/manageiq/pull/14786

Comment 4 Ilanit Stein 2017-06-12 02:56:35 EDT

Verified on CFME-5.7.3/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 credentials 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 6 errata-xmlrpc 2017-06-28 10:59:55 EDT

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:1601

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