Tracked in Github Issues as https://github.com/canonical/cloud-
init/issues/4038
** Bug watch added: github.com/canonical/cloud-init/issues #4038
https://github.com/canonical/cloud-init/issues/4038
** Changed in: cloud-init
Status: Triaged => Expired
--
You received this bug
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
> 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
** Also affects: subiquity
Importance: Undecided
Status: New
--
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
4 matches
Mail list logo