[Bug 2085070] Re: [SRU] glusterd should not be automatically restarted

[Nick Rosbrook]

** Also affects: glusterfs (Ubuntu)
   Importance: Undecided
       Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to needrestart in Ubuntu.
https://bugs.launchpad.net/bugs/2085070

Title:
  [SRU] glusterd should not be automatically restarted

Status in glusterfs package in Ubuntu:
  New
Status in needrestart package in Ubuntu:
  Incomplete
Status in glusterfs source package in Noble:
  New
Status in needrestart source package in Noble:
  Incomplete
Status in glusterfs source package in Oracular:
  New
Status in needrestart source package in Oracular:
  Incomplete
Status in glusterfs source package in Plucky:
  New
Status in needrestart source package in Plucky:
  Incomplete

Bug description:
  [ 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.

  [ Test Plan ]

   * Install glusterfs-server

   * Enable and start glusterd using systemctl

   * Then run `sudo apt reinstall libc6`

   * 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 ]

   * 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.
   ```

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/glusterfs/+bug/2085070/+subscriptions