Bug 1467864 - Refresh is not triggered after registration of Openstack node
Refresh is not triggered after registration of Openstack node
Product: Red Hat CloudForms Management Engine
Classification: Red Hat
Component: Providers (Show other bugs)
Unspecified Unspecified
unspecified Severity unspecified
: GA
: cfme-future
Assigned To: Tzu-Mainn Chen
Oleksandr Kolisnyk
Depends On:
  Show dependency treegraph
Reported: 2017-07-05 07:18 EDT by Oleksandr Kolisnyk
Modified: 2017-07-11 10:40 EDT (History)
4 users (show)

See Also:
Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2017-07-11 10:40:51 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: Openstack

Attachments (Terms of Use)

  None (edit)
Description Oleksandr Kolisnyk 2017-07-05 07:18:51 EDT
Description of problem:
Refresh of Infra provider isn't performed automatically after new node registration

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

Steps to Reproduce:
1. Go Compute -> Infrastructure -> Providers
2. Click on your Openstack Infra provider icon
3. Click Configuration -> Register Nodes
4. Upload instackenv.json file
5. Wait for refresh to be completed

Actual results:
step 4 - flash message "Nodes were added successfully. Refresh queued."
step 5 - no refresh is performed for Infra provider

Expected results:
step 5 - refresh is queued and completed successfully   

Additional info:
Comment 2 Tzu-Mainn Chen 2017-07-05 13:03:32 EDT
This is something we can't fix until the OpenStack Ironic service starts emitting events.  As far as I know, it still doesn't do so.
Comment 3 Tzu-Mainn Chen 2017-07-11 10:40:51 EDT
This is actually an OSP issue: Ironic doesn't emit events, so there's no way for CloudForms to know when a node is registered.

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