Bug 1445717 - OpenStack infra provider does not automatically refresh after being linked to a cloud provider
Summary: OpenStack infra provider does not automatically refresh after being linked to...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat CloudForms Management Engine
Classification: Red Hat
Component: Providers
Version: 5.8.0
Hardware: Unspecified
OS: Unspecified
high
medium
Target Milestone: GA
: 5.11.0
Assignee: Sam Lucidi
QA Contact: Ido Ovadia
URL:
Whiteboard: openstack
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-04-26 11:24 UTC by Ronnie Rasouli
Modified: 2019-12-12 13:33 UTC (History)
7 users (show)

Fixed In Version: 5.11.0.1
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-12-12 13:33:19 UTC
Category: Bug
Cloudforms Team: Openstack
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
last 10000 lines of evm.log (2.15 MB, text/plain)
2017-04-26 11:24 UTC, Ronnie Rasouli
no flags Details


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2019:4199 0 None None None 2019-12-12 13:33:36 UTC

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


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