Can't register new nodes after deleting old ones

[Udi Kalifon]

The notification after deleting nodes is blocking you from registering new nodes. This reproduces only randomly.

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

=> 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`.

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

[Jason E. Rist (jason-rist)]

I can't seem to reproduce this manually.

[Udi Kalifon (ukalifon)]

This doesn't happen with the latest code.

[Udi Kalifon (ukalifon)]

Still happens randomly in Ocata.

[Emilien Macchi (emilienm)]

There are no currently open reviews on this bug, changing the status back to the previous state and unassigning. If there are active reviews related to this bug, please include links in comments.

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/484706
Committed: https://git.openstack.org/cgit/openstack/tripleo-ui/commit/?id=e2373ed8e9122a2dd76c4cc422bbaafb451e798e
Submitter: Jenkins
Branch: master

commit e2373ed8e9122a2dd76c4cc422bbaafb451e798e
Author: Jiri Tomasek <email address hidden>
Date: Fri Jul 14 14:20:11 2017 +0200

    Do not show multiple notifications

    * Do not show multiple notifications when workflow sends a message
    including array of messages.
    * Allow notification message to accept array of messages
    * Update actions accordingly

    Partial-Bug: 1663243
    Change-Id: I60acd6a98fe35dad5fbdfc1474ca6f0cb41c614b

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/484382
Committed: https://git.openstack.org/cgit/openstack/tripleo-ui/commit/?id=03b835bcdb1e755cc4ba13ae2b17605ce022328a
Submitter: Jenkins
Branch: master

commit 03b835bcdb1e755cc4ba13ae2b17605ce022328a
Author: Jiri Tomasek <email address hidden>
Date: Wed Jun 28 21:56:18 2017 +0200

    MistralApiService, SwiftApiService error handling

    * Introduces axios for API requests
    * Introduces error handling refactoring which is based on handling
      errors directly in *ApiService and creating standardized Error types
      which can be handled in action thunks. handleErrors action is
      generally used to do so, but any thunk can use custom error handling
      if needed. This approach allows thunks to chain API call promises to
      different API services and catch them all in single catch statement at
      the end of the chain
    * Refactors Action thunks which use Mistral and Swift API to use chain
      of promises which are handled in single catch statement
    * updates MistralApiService, SwiftApiService to support new error
      handling

    Closes-Bug: 1663243
    Change-Id: I4e60ae8d1b29ceaf497a99313d0e2fbc6d4d1068

[OpenStack Infra (hudson-openstack)]

This issue was fixed in the openstack/tripleo-ui 7.3.0 release.