cron is not a part of the Debian cloud base bookworm image, so Bookworm based Cloud VPS instances do not have cron installed by default. However, base::standard_packages assumes it is installed everywhere, and installs a matching wmf_auto_restart service on all production hosts and all Cloud VPS VMs.
Description
Description
Details
Details
| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| Open | None | T215155 Toolforge: systemd monitoring | |||
| Resolved | MoritzMuehlenhoff | T358343 wmf_auto_restart_cron.service failing in Cloud VPS bookworm instances |
Event Timeline
Comment Actions
Change 1006917 had a related patch set uploaded (by Muehlenhoff; author: Muehlenhoff):
[operations/puppet@production] profile::base: Allow running without cron installed
Comment Actions
Change 1006917 merged by Muehlenhoff:
[operations/puppet@production] profile::base: Allow running without cron installed
Comment Actions
Change 1007328 had a related patch set uploaded (by Majavah; author: Majavah):
[operations/puppet@production] hieradata: disable cron restarts on Cloud VPS
Comment Actions
I added a new Hiera option for this:
profile::base::no_cron
If enabled, don't depend on the presence of a cron daemon. In a standard installation we still have common packages which depend on a cron-compatible daemon, but there are already use cases in Cloud VPS where cron isn't necessary. With increased adoption of systemd timers, this might also be applicable for a future baremetal installation. For now this option only omits the automated service restarts for cron.
Comment Actions
Change 1007328 merged by Majavah:
[operations/puppet@production] hieradata: disable cron restarts on Cloud VPS
Comment Actions
Mentioned in SAL (#wikimedia-cloud) [2024-03-01T14:59:28Z] <taavi> removing wmf-auto-restart-cron from all VMs without cron via cumin - https://gerrit.wikimedia.org/r/c/operations/puppet/+/1007328/ T358343