Bug 1269054

Summary: Openstack Infra refresh should not depend on openstack cloud provider status
Product: Red Hat CloudForms Management Engine Reporter: Marius Cornea <mcornea>
Component: ProvidersAssignee: Ladislav Smola <lsmola>
Status: CLOSED ERRATA QA Contact: Marius Cornea <mcornea>
Severity: high Docs Contact:
Priority: high    
Version: 5.4.0CC: cpelland, jfrey, jhardy, mfeifer, obarenbo
Target Milestone: GA   
Target Release: 5.5.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: 5.5.0.6 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-12-08 13:35:24 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-10-06 07:39:32 UTC 
Description of problem:
If the Openstack cloud provider associated with an Openstack Infra provider is not reachable then refresh fails for the infra provider, showing the error message of the cloud provider. The Infra provider refresh should not depend on the cloud provider status

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

How reproducible:
100%

Steps to Reproduce:
1. Register Openstack Infra provider
2. Register Openstack Cloud provider and assign it to the infra provider in step 1
3. Make the cloud provider inaccessible by CFME

Actual results:
The Infra provider refresh status shows 'No route to host - connect(2) (Errno::EHOSTUNREACH)' which actually refers to the cloud provider status

Expected results:
Infra provider refresh completes ok.

Additional info:
Upstream fix:
https://github.com/ManageIQ/manageiq/pull/2790
Comment 2 Ladislav Smola 2015-10-14 07:25:53 UTC 
fix stated in the description https://github.com/ManageIQ/manageiq/pull/2790
Comment 3 Marius Cornea 2015-11-20 17:02:50 UTC 
Verified in 5.5.0.11
Comment 5 errata-xmlrpc 2015-12-08 13:35:24 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