Bug 1420791 - Can't register new nodes after deleting old ones
Summary: Can't register new nodes after deleting old ones
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: openstack-tripleo-ui
Version: 11.0 (Ocata)
Hardware: Unspecified
OS: Unspecified
Target Milestone: ---
: ---
Assignee: RHOS Maint
QA Contact: Ola Pavlenko
Depends On:
TreeView+ depends on / blocked
Reported: 2017-02-09 14:01 UTC by Udi
Modified: 2017-03-23 14:26 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Last Closed: 2017-03-23 14:26:51 UTC
Target Upstream Version:

Attachments (Terms of Use)

System ID Private Priority Status Summary Last Updated
Launchpad 1663243 0 None None None 2017-02-09 15:09:03 UTC

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.

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