Closed dashmage closed 9 months ago
(by nobuto) For the record, "clear-notification" action doesn't help in this case. It can delete the message after running the action, but it will come back whenever the next update-status hook is executed.
(by nobuto) Basically the same thing as: https://bugs.launchpad.net/charm-sysconfig/+bug/1854135
But I was requested to file a new one.
(by dashmage) "clear-notification" action is now fixed. Relevant code commit here: https://git.launchpad.net/charm-sysconfig/commit/?id=6f88d54f4e62c85ea9fd2595ab45f3f6d3d64db0
juju deploy --series jammy sysconfig --config governor=performance juju add-relation sysconfig ""
Then, the sysconfig status becomes to:
This is unexpected because:
reboot is not required to apply CPU governor configuration since it can be on the fly.
the charm is very opinionated about the GRUB config but it hardcodes tty0 and ttyS0 even when the system already had those values from MAAS kernel parameters.
[/etc/default/grub.d/90-sysconfig.cfg] GRUB_CMDLINE_LINUX_DEFAULT="" GRUB_CMDLINE_LINUX_DEFAULT="$GRUB_CMDLINE_LINUX_DEFAULT console=ttyS0,115200 console=tty0"
Imported from Launchpad using lp2gh.
date created: 2023-03-23T02:23:07Z
owner: nobuto
assignee: dashmage
the launchpad url