[2.0 beta 2] If you deploy a machine in MAAS, and manually install a rack controller in it, it disappears from the machine list
Bug #1570985 reported by
Andres Rodriguez
This bug affects 2 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
MAAS |
Fix Released
|
Critical
|
Lee Trager |
Bug Description
I had a single machine MAAS deployment, and a few machines in it. I deployed a machine with Ubuntu, and then I manually converted the machine into a Rack Controller.
However, the machine automatically disappeared from the machine listing page as it was now a rack controller.
The problem with that is that I basically lost a machine and cannot re-deploy it without having to enlist / commission it again. This is a broken approach provided that I manually deployed this machine and I should have never lost it.
Related branches
lp:~ltrager/maas/rack_transitioning
- Gavin Panella (community): Approve
-
Diff: 368 lines (+253/-3)6 files modifiedsrc/maasserver/models/node.py (+22/-0)
src/maasserver/models/tests/test_node.py (+34/-0)
src/maasserver/rpc/rackcontrollers.py (+1/-2)
src/maasserver/rpc/tests/test_rackcontrollers.py (+7/-1)
src/maasserver/triggers/tests/test_websocket_listener.py (+125/-0)
src/maasserver/triggers/websocket.py (+64/-0)
Changed in maas: | |
importance: | Undecided → Critical |
milestone: | none → 2.0.0 |
Changed in maas: | |
status: | New → Confirmed |
Changed in maas: | |
status: | Confirmed → Triaged |
Changed in maas: | |
assignee: | nobody → Lee Trager (ltrager) |
status: | Triaged → In Progress |
Changed in maas: | |
status: | In Progress → Fix Committed |
Changed in maas: | |
status: | Fix Committed → Fix Released |
To post a comment you must log in.
Hmm. I vaguely remember a discussion about this. I thought it was by design.