[Bug 1060417] Re: mdadm BOOT_DEGRADED setting is ignored

[yct]

Ok, I just realized that the path /conf/conf.d/mdadm is probably a path
inside the initial RAM fs image, so it may be correct.

But I had no luck setting the bootdegraded=true parameter via GRUB kopt=
(plus running update-grub in a chroot) either.

Also there is no way to modify the kernel command line through
CloudInit, as far as I know.

So on the cloud, it would really help to have this default to "true".

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to initramfs-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1060417

Title:
  mdadm BOOT_DEGRADED setting is ignored

Status in “initramfs-tools” package in Ubuntu:
  New

Bug description:
  The file:

  /usr/share/initramfs-tools/scripts/mdadm-functions

  is supossed to check for:

  BOOT_DEGRADED="true"

  in file:

  /etc/initramfs-tools/conf.d/mdadm

  (also as per
  https://help.ubuntu.com/community/Installation/SoftwareRAID)

  however, it instead checks for it in the file:

  /conf/conf.d/mdadm

  which doesn't exit.

  Additionally, BOOT_DEGRADED should default to "true" and not "false",
  at least for the Cloud Server images, otherwise on a RAID failure, you
  are left with an unbootable production system, which kind of defies
  the point of having the RAID in the first place.

  Thanks,
  J.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1060417/+subscriptions