Bug 1467864 - Refresh is not triggered after registration of Openstack node
Summary: Refresh is not triggered after registration of Openstack node
Keywords:
Status: CLOSED CANTFIX
Alias: None
Product: Red Hat CloudForms Management Engine
Classification: Red Hat
Component: Providers
Version: 5.8.0
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: GA
: cfme-future
Assignee: Tzu-Mainn Chen
QA Contact: Oleksandr Kolisnyk
URL:
Whiteboard: openstack
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-07-05 11:18 UTC by Oleksandr Kolisnyk
Modified: 2017-07-11 14:40 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-07-11 14:40:51 UTC
Category: ---
Cloudforms Team: Openstack
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Description Oleksandr Kolisnyk 2017-07-05 11:18:51 UTC 
Description of problem:
Refresh of Infra provider isn't performed automatically after new node registration

Version-Release number of selected component (if applicable):
5.8.1.0 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 17:03:32 UTC 
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 14:40:51 UTC 
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.