If I read this correctly[0], the glusterfs version found in Bionic is EOL at upstream point of view.
For now, I would say, let's first investigate the root cause of the actual problem as usual, regardless the fact that this is EOL upstream- wise. ... but while I don't know what possible impact a newer version could have on Bionic users, it's definitely worth also investigating if upgrading glusterfs for Bionic to use a non-EOL version is viable with good rationales. # rmadison glusterfs-server | 3.13.2-1build1 | bionic/universe | amd64, arm64, armhf, i386, ppc64el, s390x glusterfs-server | 4.1.2-1 | cosmic/universe | amd64, arm64, armhf, i386, ppc64el, s390x glusterfs-server | 5.3-2 | disco/universe | amd64, arm64, armhf, i386, ppc64el, s390x [0] - https://www.gluster.org/release-schedule/ ** Also affects: glusterfs (Ubuntu Bionic) Importance: Undecided Status: New ** Changed in: glusterfs (Ubuntu Bionic) Importance: Undecided => Medium ** Changed in: glusterfs (Ubuntu Bionic) Status: New => Confirmed ** Changed in: glusterfs (Ubuntu) Status: New => Fix Released -- 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
