@mruffell thanks! Only a few comments below: > > Note because of this bug, groovy and upstream has now been changed > > to 10 min timeout, down from 1hr. > > We should decide if this is really what we want to do. And if it > should revert to the longer 1hr timeout, propose that upstream. > > I don't really know, is either default timeout better, 10 minutes or > 1 hour? @nicolasbock did you have specific reasoning for the > upstream reduction to 10 minutes?
The 10 minutes were a compromise between the default of 5 minutes (for rabbitmq-server) and what upstream thought was a very long wait of 1 hour. > If 10 minutes is what we want, then we should be ok upstream and in > Groovy, and in Focal with the current code in -proposed. In the context of the issues we are seeing with charms the 10 minute timeout should be sufficient. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1874075 Title: rabbitmq-server startup timeouts differ between SysV and systemd To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rabbitmq-server/+bug/1874075/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
