** Description changed: [Impact] When the sysstat package is pre-installed, for example on a fresh Ubuntu 24.04 installation in any cloud image, systemd presets activate the various sysstat systemd services, even when /etc/default/sysstat sets ENABLED="false". This causes a divergence between users upgrading to 24.04 from a previous release and fresh installations of 24.04. On upgrade, systemd presets do not get "re"-preset, so sysstat services are disabled. On a fresh installation, systemd presets get "re"-preset on first boot, causing the sysstat services to be enabled despite the default ENABLED="false" package setting. This results in inconsistent behaviour for users. Thanks to hideou aoi and Athos Ribeiro for finding and identifying this issue. [Fix] Instead of having packaging change the service state of the various sysstat systemd services, we use the systemd ExecCondition directive to run the services only after dynamically consulting /etc/default/sysstat. As well as the collision with systemd presets, this also resolves issues around stepping on possible user customisation in /etc/systemd/system and policy-rc.d. [Test Plan] - TBC + Covered by new dep8 test d/t/enablement [Where problems could occur] See the corresponding section in bug 2073285 for details, since risks are best considered with the two changes we’re making together.
-- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2073284 Title: sysstat service enablement state mismatches debconf and /etc/default/sysstat setting To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-release-notes/+bug/2073284/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
