MAAS

set_boot_disk websocket method does not result in machine update notify

Bug #1912722 reported by Caleb Ellis
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
MAAS
Status tracked in 3.6
3.0
Won't Fix
Medium
Unassigned
3.5
Won't Fix
Medium
Unassigned
3.6
Triaged
Medium
Unassigned
MAAS 3.6.x
maas-ui
Triaged
Medium
Unassigned
maas-ui 3.6.x

Bug Description

Calling machine.set_boot_disk successfully sets the boot disk, however the machine update is not broadcast through the websocket. In the legacy UI this wasn't obvious because it used radio buttons to set boot disks, but this pattern is not great because the "source of truth" gets muddled between the database and the UI.

Alberto Donato (ack)
Changed in maas:
importance: Undecided → High
status: New → Triaged
milestone: none → 3.0.1
Mauricio Faria de Oliveira (mfo)
Changed in maas:
milestone: 3.0.1 → none
Revision history for this message
Adam Collard (adam-collard) wrote :

Let's update the TRIGGER code to include the boot_disk id when looking for changes

Changed in maas:
importance: High → Medium
Changed in maas-ui:
importance: Undecided → Medium
milestone: none → 3.5.0
status: New → Triaged
Changed in maas:
milestone: none → 3.1.2
milestone: 3.1.2 → 3.5.0
Anton Troyanov (troyanov)
Changed in maas:
milestone: 3.5.0 → 3.5.x
Changed in maas-ui:
milestone: 3.5.0 → 3.5.x
Anton Troyanov (troyanov)
Changed in maas-ui:
milestone: 3.5.x → 3.6.x
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

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