Please provide a rescue/recovery mode
Bug #1403257 reported by
James Troup
This bug affects 10 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
MAAS |
Fix Released
|
Wishlist
|
Newell Jensen |
Bug Description
One of our servers is offline for silly reasons¹. If I could get to
the console, I could trivially fix this, but MAAS doesn't make it
easy/possible for me to do so. Before we used MAAS, I would have
netbooted the box into a rescue environment.
It'd be really useful if MAAS offered the ability to do a one time net
boot into a rescue/
the machine's state but gave the user a hope of fixing things
remotely.
¹ I removed a disk array from the machine but forgot to edit
/etc/fstab and mountall has insane defaults and will hang forever
waiting for the disk array to magically reappear.
Changed in maas: | |
importance: | Undecided → Wishlist |
status: | New → Triaged |
tags: | added: canonical-bootstack |
tags: | added: canonical-is |
Changed in maas: | |
milestone: | none → 2.1.0 |
status: | Triaged → Fix Committed |
Changed in maas: | |
milestone: | 2.0.1 → 2.1.0 |
Changed in maas: | |
status: | Fix Committed → Fix Released |
Changed in maas: | |
assignee: | nobody → Newell Jensen (newell-jensen) |
To post a comment you must log in.
We ran into this as well today, where a maas-deployed host had a failed disk which caused additional problems with the box. The bad disk is still in fstab and the ilo is not allowing us to intercept the grub prompt to go into a rescue and edit the fstab file, rendering the box unbootable without physical intervention. It would be awesome if we could boot a recovery and fix fstab.