Bug 1390660

Summary: status last refresh error: Unable to obtain a collection: 'stacks' in a service 'orchestration' through API. Please, fix your OpenStack...
Product: Red Hat CloudForms Management Engine Reporter: Ronnie Rasouli <rrasouli>
Component: ProvidersAssignee: Tzu-Mainn Chen <tzumainn>
Status: CLOSED DUPLICATE QA Contact: Ola Pavlenko <opavlenk>
Severity: low Docs Contact:
Priority: low    
Version: 5.7.0CC: dajohnso, jfrey, jhardy, obarenbo, rrasouli
Target Milestone: GA   
Target Release: cfme-future   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard: openstack:stack:provision
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-12-07 07:11:15 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: Openstack Target Upstream Version:
Attachments:
Description Flags
error from evm.log catching filtered by stacks none

Description Ronnie Rasouli 2016-11-01 15:45:28 UTC
Created attachment 1216149 [details]
error from evm.log catching filtered by stacks

Description of problem:

Cloud provider show the following error in RHOS10 deployment.

Unable to obtain a collection: 'stacks' in a service 'orchestration' through API. Please, fix your OpenStack...

No applied stack on the cloud provider

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


How reproducible:


Steps to Reproduce:
1.configure openstack RHOS10 as cloud provider
2.perform refresh configuration --> refresh provider...


Actual results:

Error in last refresh status

Expected results:

no un related errors 

Additional info:

Comment 2 Tzu-Mainn Chen 2016-11-08 15:42:50 UTC
I see the following in the log:

"The server didn't respond in time."

That looks like an OpenStack issue - can you test if your OpenStack CLI works?  If not, then your OpenStack may have some issues.

Comment 3 Ronnie Rasouli 2016-12-07 07:11:15 UTC

*** This bug has been marked as a duplicate of bug 1402028 ***