Bug 1265590

Summary:	Openstack infra provider refresh depends on the associated cloud provider status
Product:	Red Hat CloudForms Management Engine	Reporter:	Marius Cornea <mcornea>
Component:	Providers	Assignee:	Ladislav Smola <lsmola>
Status:	CLOSED ERRATA	QA Contact:	Milan Falešník <mfalesni>
Severity:	high	Docs Contact:
Priority:	high
Version:	5.4.0	CC:	jfrey, jhardy, mcornea, obarenbo, simaishi
Target Milestone:	GA
Target Release:	5.5.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	5.5.0.1	Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2015-12-08 13:32:55 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:

Description Marius Cornea 2015-09-23 10:10:59 UTC

Description of problem:
Openstack infra provider refresh depends on the associated cloud provider status. For example if the Openstack Cloud provider which is associated to the infra provider cannot be reached the refresh for the infra provider will show a 'Errno::EHOSTUNREACH' which actually refers to the cloud provider. Same thing goes for other errors such as authentication.
 

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

How reproducible:
100%

Steps to Reproduce:
1. Add Openstack Infra provider
2. Add Openstack Cloud provider and associate it to the infra provider added in step 1
3. Bring down the cloud provider added in step 2
4. Run refresh on the infra provider

Actual results:
Refresh fails with the error message of the cloud provider

Expected results:
Refresh completes ok.

Additional info:

Comment 2 Ladislav Smola 2015-10-30 08:41:28 UTC

@marius I just tested this and it appears to be fixed

this is the upstream fix https://github.com/ManageIQ/manageiq/pull/2790

Comment 3 Marius Cornea 2015-10-30 08:48:33 UTC

Yep, looks so but that the patch is not present in the downstream 5.4 product.

Comment 4 Milan Falešník 2015-11-13 14:46:05 UTC

I have verified this in 5.5.0.10. I have added and refreshed both Openstack providers, then I blocked the Overcloud IP in the firewalld and ran a refresh on the infra provider.

Comment 6 errata-xmlrpc 2015-12-08 13:32:55 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-2015:2551