Comment 2 for bug 1993503

Hi Brett,

this involves subiquity since it seeds cloud-init through user-data. subiquity's fault is to not skip cc_grub_dpkg by adding 'grub_dpkg: {enabled: false}' to user-data. The users choice in subiquity on where to install grub is to be overridden by cc_grub_dpkg on first boot.
Form my point of view subiquity could either skip user choice and stick with auto-detection (like cc_grub_dpkg is doing by default) or let the user choose on witch disk grub is installed onto. In the auto-detection case cc_grub_dpkg is to be skipped since the installer already did auto-detection with an at least equally good mechanism. In the other case cc_grub_dpkg has to be skipped since cc_grub_dpkg auto-detection is over-ridding the users choice.