yahoo-eng-team team mailing list archive

[Chad Smith <1993503@xxxxxxxxxxxxxxxxxx>]

Thanks for the detailed discussions here @danielky.

I think I agree with your last statement in comment #3


> Detecting the raid-setup and the right disks might be out of scope for cc_grub_dpkg, so why not just skip setting the "grub-pc/install_devices" item if it is already set in debconf and there is no "grub-pc/install_devices" given in cc_grub_dpkg config?

In the case of the live installer, subiquity (via curtin) ends up
setting grub debconf selections. I do think cloud-init's
cc_grub_dpkg::fetcg_idevs function[1] could probably grow awareness of
debconf selections as that should be honored with precedence above local
discovery using grub probe.

I'll set this to triaged and confirm with the team tomorrow that this is
a reasonable approach/consensus for cloud-init.


As for the subiquity aspect of this bug, I agree is seems like providing either:

grub_dpkg:
  enabled: false

-- or --
# reflecting the specific devices that were chosen during auto install would make the most sense to ensure the system boots properly configured and cloud-init does not overwrite values setup by the installer (via curtin)

grub_dpkg:
  grub-pc/install_devices: <dev1> <dev2>



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

** Changed in: cloud-init
   Importance: Undecided => Medium

-- 
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:
  Triaged
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