Deploying charm-sysconfig with ubuntu 22.04 results in the charm going into blocked status with the message: update-grub and reboot required. Changes in /etc/default/grub.d/90-sysconfig.cfg. But the 90-sysconfig.cfg file does not contain any specific config apart from some comments.
Upon SSH-ing into the unit, it looked like there was a difference between /etc/boot/grub.cfg and the grub config rendered using grub-mkconfig (which the charm uses to check whether there were any changes so it can notify for a reboot).
Deploying charm-sysconfig with ubuntu 22.04 results in the charm going into blocked status with the message:
update-grub and reboot required. Changes in /etc/default/grub.d/90-sysconfig.cfg
. But the90-sysconfig.cfg
file does not contain any specific config apart from some comments.Upon SSH-ing into the unit, it looked like there was a difference between
/etc/boot/grub.cfg
and the grub config rendered usinggrub-mkconfig
(which the charm uses to check whether there were any changes so it can notify for a reboot).Diff output: https://pastebin.ubuntu.com/p/DPCyQK55mj/
A similar problem had been resolved with the systemd conf file here: bug report, MP.
From the diff, we can see that there is somehow a difference in the way the root fs is being referenced (with the
LABEL
or withUUID
).