Interesting fact, while testing the installation of glusterfs-server in Cosmic:
# COSMIC Adding group `gluster' (GID 117) ... Done. Setting up glusterfs-client (4.1.2-1) ... Setting up glusterfs-server (4.1.2-1) ... glusterd.service is a disabled or a static unit, not starting it. glustereventsd.service is a disabled or a static unit, not starting it. Processing triggers for libc-bin (2.28-0ubuntu1) ... Processing triggers for systemd (239-7ubuntu10.13) ... # COSMIC: debian/rules +override_dh_systemd_enable: + dh_systemd_enable --no-enable --name=glusterd + dh_systemd_enable --no-enable --name=glustereventsd In Cosmic glustereventsd is disabled by default after installation, as oppose to Bionic. Maybe there is a reasons for that behaviour change at installation. Might be worth to investigate further that aspect IMHO. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1830615 Title: glusterfs-server 3.13.2-1build1 installation fails in Bionic because starting up the glustereventsd.service times out To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glusterfs/+bug/1830615/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
