cpufrequtils updates: are reboots needed?
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| charm-sysconfig |
New
|
Medium
|
Unassigned | ||
Bug Description
I haven't looked deeply enough to determine if this a bug for sure or not, but it does seem a little "off".
While working on providing updates to this charm, I noticed that changes related to cpufrequtils both resort in host.service_
I'm not close enough to the functionality in question to be comfortable enough to change this outright, but it seems that if a reboot is needed, a service restart is perhaps of limited use, while if a service restart is adequate, a reboot is unneeded.
If a host restart is not needed here, I'd suggest replacing the self._render_
| Changed in charm-sysconfig: | |
| importance: | Undecided → Medium |
| Yoshi Kadokawa (yoshikadokawa) wrote | #1 |
I'm seeing and thinking the same for this.
I have only configured the following for sysconfig charm, and seeing the following juju status message "reboot required. Changes in: /etc/systemd/
in addition to this the application status is in "blocked" status as well.
$ juju config sysconfig governor=
For now the workaround is to run clear-notification action.