Bug 1420791

Summary: Can't register new nodes after deleting old ones
Product: Red Hat OpenStack Reporter: Udi <ukalifon>
Component: openstack-tripleo-uiAssignee: RHOS Maint <rhos-maint>
Status: CLOSED WORKSFORME QA Contact: Ola Pavlenko <opavlenk>
Severity: urgent Docs Contact:
Priority: unspecified    
Version: 11.0 (Ocata)CC: jjoyce, jschluet, slinaber, tvignaud
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-03-23 14:26:51 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description Udi 2017-02-09 14:01:16 UTC
Description of problem:
The notification after deleting nodes is blocking you from registering new nodes.

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

How reproducible:

Steps to Reproduce:
1. Delete all the nodes
2. Open the register nodes dialog
3. Click "Add New"

Actual results:
The button doesn't respond and you can't register a new node. You see this exception in the console:

invariant.js:44 Uncaught Invariant Violation: Objects are not valid as a React child (found: [object XMLHttpRequest]). If you meant to render a collection of children, use an array instead or wrap the object using createFragment(object) from the React add-ons. Check the render method of `Notification`.

Additional info:
F5 after delete nodes works around this, but this is a blocker for the automation.

Comment 1 Ola Pavlenko 2017-03-23 14:26:51 UTC
Latest from Udi:
This doesn't happen with the latest code.