** Attachment added:
"BakkersteamServicesHandtekening_5753069d-88c4-4c40-beac-69286b4c6a54.png"
https://bugs.launchpad.net/bugs/2085070/+attachment/5844110/+files/BakkersteamServicesHandtekening_5753069d-88c4-4c40-beac-69286b4c6a54.png
** Attachment added: "iso27001_935810b9-e91d-44b6-a223-50
its a chain
the glusterd takes a bit of time to initialize, for that reason the mount has
the
Requires=glusterd.service
After=glusterd.service
It was the only way I would always have the FS mounted after a reboot,
without it, it would be a hit/mis.
An application requiring the mount has a
just to clarify and so you can reproduce it
1) a mount unit to mount a glusterfs shared.mount
[Unit]
Description=Mount GlusterFS Volume /shared
Requires=glusterd.service
After=glusterd.service
2) an application (java) unit that needs the /shared
[Unit]
Description=Application Service
After=ne
Public bug reported:
As requested in https://discourse.ubuntu.com/t/needrestart-changes-in-
ubuntu-24-04-service-restarts/44671
Glusterd should not automaticly restart after an update.
Other services can depend on it and because of that also get an unwanted /
unplanned restart.
besides I don't t
