intrepid upgrade of mdadm should default BOOT_DEGRADED to false
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| mdadm (Ubuntu) |
Fix Released
|
High
|
Unassigned | ||
Bug Description
Binary package hint: mdadm
Intrepid adds support to mdadm, grub, and initramfs-tools to allow an administrator to configure a system with / or /boot on an md device to either boot when a new degraded array event happens, or not.
The legacy behavior has been to hold a system with a newly degraded array at the initramfs busybox prompt.
Users upgrading to intrepid would expect the same behavior, thus, we need to default that behavior to BOOT_DEGRADED=false on upgrades.
Note the following:
* Any system administrator can change this behavior after the fact using `dpkg-reconfigure mdadm`
* Any intrepid system with / or /boot on an md device, which reboots and finds a newly missing disk will be held at a prompt for 15 seconds asking "Do you want to boot the degraded RAID?"
:-Dustin
| Changed in mdadm: | |
| importance: | Undecided → High |
| status: | New → In Progress |
| Dustin Kirkland (kirkland) wrote | #1 |
| Dustin Kirkland (kirkland) wrote | #2 |
| Launchpad Janitor (janitor) wrote | #3 |
| Changed in mdadm: | |
| status: | In Progress → Fix Released |
Patch attached, requesting sponsorship.
:-Dustin