1.9.0 node status on listing page doesn't match node status on node details page

Bug #1548390 reported by Carla Berkers
12
This bug affects 1 person
Affects Status Importance Assigned to Milestone
MAAS
Won't Fix
High
Unassigned

Bug Description

I want to release a node that is in the "failed commissioning" state, but that action is not available to me.

Then I try to mark it fixed, and that action is not available to me either.

Then I go to node details and see the state of the node is "Broken"

Tags: ui
Revision history for this message
Blake Rouse (blake-rouse) wrote :

This is disturbing. Can you provide the MAAS version this occurred on? Can you try to see if you can reproduce this behavior? If possible to reproduce can you provide the MAAS logs as well as the browser console log?

Changed in maas:
status: New → Triaged
importance: Undecided → High
milestone: none → 2.0.0
tags: added: ui
Changed in maas:
status: Triaged → Incomplete
summary: - node status on listing page doesn't match node status on node details
- page
+ 1.9.0 node status on listing page doesn't match node status on node
+ details page
Revision history for this message
Andres Rodriguez (andreserl) wrote :

Also, please provide a screenshot!

Changed in maas:
status: Incomplete → Triaged
status: Triaged → Incomplete
Changed in maas:
status: Incomplete → Won't Fix
milestone: 2.0.0 → none
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

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