After providing a node, the node is unavailable for any action on UI

Bug #1672834 reported by opavlenk
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
tripleo
Expired
Undecided
Unassigned

Bug Description

Description of problem:
After providing a node on UI, spin works forever, even after refresh results. Any node action is unavailable, introspection, tagging, or role-node assignment from the main screen.

Steps to Reproduce:
1. provide a registered node
2. introspect any other node
3. assign the provided node to a role

Actual results:
the provided node status changed to available.
the node is shown on the main page as available for assignment.
nodes spin works forever on nodes screen and on role-nodes assignment window.
any other node related action is unavailable on UI.

Expected results:
the provided node status changed to available.
the node is shown on the main page as available for assignment.
node could be assigned to a role.
any other node could be introspected.

Additional info:
works after page refresh

Tags: ui
Changed in tripleo:
milestone: none → pike-1
importance: Undecided → Medium
status: New → Triaged
Changed in tripleo:
milestone: pike-1 → pike-2
Changed in tripleo:
milestone: pike-2 → pike-3
Changed in tripleo:
milestone: pike-3 → pike-rc1
Changed in tripleo:
milestone: pike-rc1 → queens-1
Changed in tripleo:
milestone: queens-1 → queens-2
Changed in tripleo:
milestone: queens-2 → queens-3
Changed in tripleo:
milestone: queens-3 → queens-rc1
Changed in tripleo:
milestone: queens-rc1 → rocky-1
Changed in tripleo:
milestone: rocky-1 → rocky-2
Changed in tripleo:
milestone: rocky-2 → rocky-3
Changed in tripleo:
milestone: rocky-3 → rocky-rc1
Changed in tripleo:
milestone: rocky-rc1 → stein-1
Changed in tripleo:
milestone: stein-1 → stein-2
Revision history for this message
Emilien Macchi (emilienm) wrote : Cleanup EOL bug report

This is an automated cleanup. This bug report has been closed because it
is older than 18 months and there is no open code change to fix this.
After this time it is unlikely that the circumstances which lead to
the observed issue can be reproduced.

If you can reproduce the bug, please:
* reopen the bug report (set to status "New")
* AND add the detailed steps to reproduce the issue (if applicable)
* AND leave a comment "CONFIRMED FOR: <RELEASE_NAME>"
  Only still supported release names are valid (FUTURE, PIKE, QUEENS, ROCKY, STEIN).
  Valid example: CONFIRMED FOR: FUTURE

Changed in tripleo:
importance: Medium → Undecided
status: Triaged → Expired
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.