Right now for cloud images, the flow of editing /etc/default/grub to modify GRUB_CMDLINE_LINUX_DEFAULT and then running update-grub simply doesn't work.
It feels like either a warning in /etc/default/grub or having 50-cloudimg-settings.cfg edited to forward existing cmdline arguments seems like the path of least surprise for that value. For values that aren't appendable, like the OP's GRUB_TIMEOUT, a comment pointing the user to /etc/default/grub.d would be really useful. All /etc/default/grub says to do after editing the file is run update- grub. When that doesn't work, the user is going to be surprised! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1871186 Title: grub-mkconfig prefers /etc/default/grub.d settings To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1871186/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
