** Merge proposal linked:
https://code.launchpad.net/~r41k0u/ubuntu/+source/needrestart/+git/needrestart/+merge/478237
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2085070
Title:
[SRU] glusterd
** Merge proposal unlinked:
https://code.launchpad.net/~r41k0u/ubuntu/+source/needrestart/+git/needrestart/+merge/478237
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2085070
Title:
[SRU] gluste
** Merge proposal linked:
https://code.launchpad.net/~r41k0u/ubuntu/+source/needrestart/+git/needrestart/+merge/478237
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2085070
Title:
[SRU] glusterd
** 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
This bug was fixed in the package needrestart - 3.6-8ubuntu7
---
needrestart (3.6-8ubuntu7) plucky; urgency=medium
* Don't restart glusterd automatically (LP: #2085070)
- d/p/lp2085070/0020-ubuntu-avoid-restart-glusterd.patch:
Add regex to ignore glusterd and for automatic
I have uploaded a patch for the devel series (plucky) for now. But
before we try to push an SRU through, I would like to dig more into the
restart-ability of glusterd.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launch
** Also affects: glusterfs (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2085070
Title:
[SRU] glusterd should not be automatically restarted
To
The After= makes complete sense. It's the Requires= I am not sure of.
Have you tried without that? Or maybe use Wants= instead?
If glusterd.service is safe to restart (i.e. won't disrupt the mount),
then it should be allowed to do so. Removing Requires= would prevent
dependent services from being
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
Is it really necessary for the mount unit to Requires=glusterd.service?
Does restarting glusterd.service actually make the shared mount
unusable?
If you remove the Requires=glusterd.service (or the
Requires=shared.mount on the other unit), and restart glusterd.service,
does everything carry on OK?
** Also affects: needrestart (Ubuntu Noble)
Importance: Undecided
Status: New
** Also affects: needrestart (Ubuntu Oracular)
Importance: Undecided
Status: New
** Also affects: needrestart (Ubuntu Plucky)
Importance: Undecided
Assignee: Pragyansh Chaturvedi (r41k0u)
** Summary changed:
- [SRU] glusterd and keepalived should not be automatically restarted
+ [SRU] glusterd should not be automatically restarted
** Description changed:
[ Impact ]
* glusterd.service should not be automatically restarted after an update as
other services which depen
12 matches
Mail list logo
