** Description changed: [Impact] glusterfs-server is not "installable" in Bionic/18.04 LTS. [Test case] 1. Run Bionic 2. Install glusterfs-server -- apt-get install glusterfs-server ... Job for glustereventsd.service failed because a timeout was exceeded. See "systemctl status glustereventsd.service" and "journalctl -xe" for details. invoke-rc.d: initscript glustereventsd, action "start" failed. ● glustereventsd.service - LSB: Gluster Events Server Loaded: loaded (/etc/init.d/glustereventsd; generated) Active: failed (Result: timeout) since Mon 2019-05-27 09:52:15 UTC; 15ms ago Docs: man:systemd-sysv-generator(8) Process: 17909 ExecStart=/etc/init.d/glustereventsd start (code=killed, signal=TERM) Tasks: 3 (limit: 4915) CGroup: /system.slice/glustereventsd.service ├─17927 /usr/bin/python /usr/sbin/glustereventsd -p /var/run/glustereventsd.pid └─17931 /usr/bin/python /usr/sbin/glustereventsd -p /var/run/glustereventsd.pid May 27 09:47:14 vm1 systemd[1]: Starting LSB: Gluster Events Server... May 27 09:47:14 vm1 glustereventsd[17909]: * Starting glustereventsd service glustereventsd dpkg: error processing package glusterfs-server (--configure): installed glusterfs-server package post-installation script subprocess returned error exit status 1 Processing triggers for libc-bin (2.27-3ubuntu1) ... Processing triggers for ureadahead (0.100.0-20) ... Processing triggers for systemd (237-3ubuntu10.15) ... Errors were encountered while processing: glusterfs-server E: Sub-process /usr/bin/dpkg returned an error code (1) dpkg -l | grep gluster ii glusterfs-client 3.13.2-1build1 amd64 clustered file-system (client package) ii glusterfs-common 3.13.2-1build1 amd64 GlusterFS common libraries and translator modules iF glusterfs-server 3.13.2-1build1 amd64 clustered file-system (server package) systemctl status glustereventsd.service ● glustereventsd.service - LSB: Gluster Events Server Loaded: loaded (/etc/init.d/glustereventsd; generated) Active: failed (Result: timeout) since Mon 2019-05-27 09:52:15 UTC; 2min 9s ago Docs: man:systemd-sysv-generator(8) CGroup: /system.slice/glustereventsd.service ├─17927 /usr/bin/python /usr/sbin/glustereventsd -p /var/run/glustereventsd.pid └─17931 /usr/bin/python /usr/sbin/glustereventsd -p /var/run/glustereventsd.pid May 27 09:47:14 vm1 systemd[1]: Starting LSB: Gluster Events Server... May 27 09:47:14 vm1 glustereventsd[17909]: * Starting glustereventsd service glustereventsd May 27 09:52:15 vm1 systemd[1]: glustereventsd.service: Start operation timed out. Terminating. May 27 09:52:15 vm1 systemd[1]: glustereventsd.service: Failed with result 'timeout'. May 27 09:52:15 vm1 systemd[1]: Failed to start LSB: Gluster Events Server. -- [Regression Potential] The fix is dropping the sysv/upstart approach in favor of systemd approach. Most modern debian/ubuntu package of glusterfs-server have glusterd & glustereventsd disabled voluntary, and require manual operation to either start it or enable it. Since it's already in place is Cosmic and late as-is, it makes sense to me to stay consistent with what we have in later version. All documentation I have seen so far, indicate that glustereventsd need to be enable using systemctl enable too, so that approach seems align with official documentation found online. The only downside, that I can see, is that one shouldn't expect "glusterd" and "glustereventsd" to be up and running after the installation. It's a behaviour change per see, but in fact, since the current package never been into a installable/useable state in Bionic, then it's a behaviour change that no one (or very little for those who might have workaround the install issue) will notice since again nobody was able to install the package in Bionic so far. The other option will be to upgrade the package to a non EOL version, but same change behaviour will occur (same approach is used) but + code change. I don't know how this code change may or may not impact Bionic user, this will require more analysis. The upgrade can also be part of a separate discussion, let's focus for now on fixing the installation IMHO. + Additionally, the package have never been able to be installed successfully in Bionic, so who knows what bugs this version might have, once installed. Of course, I did and will continue to do more testing once found in bionic-proposed, but if a bug arise, this will need to be fix as any other userspace bug. I don't see a big problem here. + [Other Info] # General info about events api: https://docs.gluster.org/en/latest/Administrator%20Guide/Events%20APIs/ Events API feature is integrated with GD2. Webhooks can be registered to listen for GlusterFS events. # Bug itself: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=875651 https://launchpad.net/bugs/1712748 # EOL related: https://www.gluster.org/release-schedule/ https://docs.gluster.org/en/latest/release-notes/4.0.0/ As 3.13 was a short term maintenance release, features which have been included in that release are available with 4.0.0 as well. [Original Description] glusterfs-server installation fails on Bionic apt-get install glusterfs-server ... Job for glustereventsd.service failed because a timeout was exceeded. See "systemctl status glustereventsd.service" and "journalctl -xe" for details. invoke-rc.d: initscript glustereventsd, action "start" failed. ● glustereventsd.service - LSB: Gluster Events Server Loaded: loaded (/etc/init.d/glustereventsd; generated) Active: failed (Result: timeout) since Mon 2019-05-27 09:52:15 UTC; 15ms ago Docs: man:systemd-sysv-generator(8) Process: 17909 ExecStart=/etc/init.d/glustereventsd start (code=killed, signal=TERM) Tasks: 3 (limit: 4915) CGroup: /system.slice/glustereventsd.service ├─17927 /usr/bin/python /usr/sbin/glustereventsd -p /var/run/glustereventsd.pid └─17931 /usr/bin/python /usr/sbin/glustereventsd -p /var/run/glustereventsd.pid May 27 09:47:14 vm1 systemd[1]: Starting LSB: Gluster Events Server... May 27 09:47:14 vm1 glustereventsd[17909]: * Starting glustereventsd service glustereventsd dpkg: error processing package glusterfs-server (--configure): installed glusterfs-server package post-installation script subprocess returned error exit status 1 Processing triggers for libc-bin (2.27-3ubuntu1) ... Processing triggers for ureadahead (0.100.0-20) ... Processing triggers for systemd (237-3ubuntu10.15) ... Errors were encountered while processing: glusterfs-server E: Sub-process /usr/bin/dpkg returned an error code (1) dpkg -l | grep gluster ii glusterfs-client 3.13.2-1build1 amd64 clustered file-system (client package) ii glusterfs-common 3.13.2-1build1 amd64 GlusterFS common libraries and translator modules iF glusterfs-server 3.13.2-1build1 amd64 clustered file-system (server package) systemctl status glustereventsd.service ● glustereventsd.service - LSB: Gluster Events Server Loaded: loaded (/etc/init.d/glustereventsd; generated) Active: failed (Result: timeout) since Mon 2019-05-27 09:52:15 UTC; 2min 9s ago Docs: man:systemd-sysv-generator(8) CGroup: /system.slice/glustereventsd.service ├─17927 /usr/bin/python /usr/sbin/glustereventsd -p /var/run/glustereventsd.pid └─17931 /usr/bin/python /usr/sbin/glustereventsd -p /var/run/glustereventsd.pid May 27 09:47:14 vm1 systemd[1]: Starting LSB: Gluster Events Server... May 27 09:47:14 vm1 glustereventsd[17909]: * Starting glustereventsd service glustereventsd May 27 09:52:15 vm1 systemd[1]: glustereventsd.service: Start operation timed out. Terminating. May 27 09:52:15 vm1 systemd[1]: glustereventsd.service: Failed with result 'timeout'. May 27 09:52:15 vm1 systemd[1]: Failed to start LSB: Gluster Events Server. The issue is also reported here: https://github.com/gluster/glusterfs-debian/issues/22
-- 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
