yahoo-eng-team team mailing list archive

[Brett Holman <1993503@xxxxxxxxxxxxxxxxxx>]

> This is only possible for autoinstall. This bugreport is partly about
why disabling grub_dpkg in user-data better be the default for both
manual- and auto-install.

Since the requested behavior change can be driven by different user-data
from subiquity, I think this doesn't require cloud-init changes.

Since this doesn't require changes to cloud-init, and cloud-init will
not run this module unless configured to do so, I'm setting this bug to
invalid for cloud-init. I believe this to be a subiquity change.

Please update this bug if you think this is incorrect.

** Changed in: cloud-init
       Status: New => Invalid

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to cloud-init.
https://bugs.launchpad.net/bugs/1993503

Title:
  grub_dpkg writes wrong device into debconf

Status in cloud-init:
  Invalid
Status in subiquity:
  New

Bug description:
  After auto-installing ubuntu 22.04 onto a LV on a mdraid 1 with two
  disks cc_grub_dpkg overrides the correct `grub-pc/install_devices`
  debconf entry with a false one on first boot:

  ```
  ~# debconf-show grub-pc | grep grub-pc/install_devices:
  * grub-pc/install_devices: /dev/disk/by-id/dm-name-vg0-lv_root
  ```

  This breaks grub updates.

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1993503/+subscriptions