Bug 1445717

Summary: OpenStack infra provider does not automatically refresh after being linked to a cloud provider
Product: Red Hat CloudForms Management Engine Reporter: Ronnie Rasouli <rrasouli>
Component: ProvidersAssignee: Sam Lucidi <slucidi>
Status: CLOSED ERRATA QA Contact: Ido Ovadia <iovadia>
Severity: medium Docs Contact:
Priority: high    
Version: 5.8.0CC: jfrey, jhardy, obarenbo, rrasouli, simaishi, slucidi, smallamp
Target Milestone: GA   
Target Release: 5.11.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard: openstack
Fixed In Version: 5.11.0.1 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2019-12-12 13:33:19 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: Bug
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: Openstack Target Upstream Version:
Embargoed:
Attachments:
Description Flags
last 10000 lines of evm.log none

Description Ronnie Rasouli 2017-04-26 11:24:19 UTC
Created attachment 1274176 [details]
last 10000 lines of evm.log

Description of problem:

compute node does not display the instance count at all

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

How reproducible:


Steps to Reproduce:
1. link between cloud provider and infra provider
2. navigate to compute --> infra --> nodes


Actual results:
Nodes does not display on quad icon nor on Relationships the number of instances (VM)

Expected results:
Display instances properly

Additional info:

Comment 4 Tzu-Mainn Chen 2017-04-27 13:30:08 UTC
Okay, looks like the real issue is that the infra provider does not immediately refresh after being linked to a cloud provider, leading to a delay before VMs appear for nodes.

Comment 7 Ido Ovadia 2019-07-17 11:00:19 UTC
Verified
========
5.11.0.14

Comment 9 errata-xmlrpc 2019-12-12 13:33:19 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/RHBA-2019:4199