[Bug 1867386] Please test proposed package
Corey Bryant
1867386 at bugs.launchpad.net
Wed May 27 12:33:03 UTC 2020
Hello Tiago, or anyone else affected,
Accepted ceph into train-proposed. The package will build now and be
available in the Ubuntu Cloud Archive in a few hours, and then in the
-proposed repository.
Please help us by testing this new package. To enable the -proposed
repository:
sudo add-apt-repository cloud-archive:train-proposed
sudo apt-get update
Your feedback will aid us getting this update out to other Ubuntu users.
If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, and change the tag
from verification-train-needed to verification-train-done. If it does
not fix the bug for you, please add a comment stating that, and change
the tag to verification-train-failed. In either case, details of your
testing will help us make a better decision.
Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in
advance!
** Changed in: cloud-archive/train
Status: Triaged => Fix Committed
** Tags added: verification-train-needed
--
You received this bug notification because you are a member of Ubuntu
OpenStack, which is subscribed to Ubuntu Cloud Archive.
https://bugs.launchpad.net/bugs/1867386
Title:
Beast frontend does not allow tuning of maximum backlog of pending
connections
Status in Ubuntu Cloud Archive:
Fix Released
Status in Ubuntu Cloud Archive stein series:
Fix Committed
Status in Ubuntu Cloud Archive train series:
Fix Committed
Status in Ubuntu Cloud Archive ussuri series:
Fix Released
Status in ceph package in Ubuntu:
Fix Released
Status in ceph source package in Disco:
Won't Fix
Status in ceph source package in Eoan:
Fix Committed
Status in ceph source package in Focal:
Fix Released
Bug description:
[Impact]
Currently, RGW has no option to configure the maximum size for the
queue of connections waiting to be accepted when using the Beast
frontend. Instead, it uses the value from
boost::asio::socket_base::max_connections.
[Test Case]
Add the 'max_connection_backlog' config option to the RGW beast
frontend configuration and check that it is ignored and not used.
[Regression Potential]
This change has been reviewed upstream and have been passed through
the usual upstream ceph QA tests.
[Other info]
This bug is similar to 1838109, which reports the same issue but for
the civetweb frontend.
Ceph tracker bug: https://tracker.ceph.com/issues/43952
Upstream PRs:
https://github.com/ceph/ceph/pull/33053
https://github.com/ceph/ceph/pull/33340
https://github.com/ceph/ceph/pull/33341
To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-archive/+bug/1867386/+subscriptions
More information about the Ubuntu-openstack-bugs
mailing list