** 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 depend on it will also get an unplanned restart.
  
   * This change adds a regex pattern for glusterd.service in the default
     needrestart.conf to prevent it's automatic restart.
  
-  * Similarly, as reported in #2089155, keepalived must not be automatically
-    restarted as other services depending on it's presence and status quo may
-    be disrupted
- 
  [ Test Plan ]
  
-  * Install glusterfs-server and keepalived
+  * Install glusterfs-server
  
-  * Enable and start glusterd using systemctl
- 
-  * Create /etc/keepalived/keepalived.conf and add some sample text in it
- after ! (essentially a comment)
- 
-  * Enable and start keepalived using systemctl (it might get stuck while
- starting, just interrupt it using Ctrl-C)
+  * Enable and start glusterd using systemctl
  
   * Then run `sudo apt reinstall libc6`
  
-  * glusterd.service, keepalived.service will appear under `Restarting 
services...`, while it
+  * glusterd.service will appear under `Restarting services...`, while it
     should actually appear under `Service restarts being deferred:`
  
  [ Where problems could occur ]
  
   * The original bug reporter thinks that only glusterd.service must be
     excluded from restarting. There might be other glusterfs related services
     that might be restarting, but they haven't shown up during testing.
     (I tested with glustereventsd.service, gluster-ta-volume.service,
     glusterfssharedstorage.service and glusterd.service. Other services are not
     restarting)
  
  [ Other Info ]
  
-  * For keepalived:
- https://bugs.launchpad.net/ubuntu/+source/needrestart/+bug/2089155
- 
-  * For glusterd: original bug report:
+  * Original bug report:
   ```
   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 think its smart to restart a FS which is basicly what you 
are doing.
   ```

-- 
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 manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/needrestart/+bug/2085070/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to