Description of problem:
Ceph's RGW uses curl_multi_wait and hits a deadlock in this code (bug 1327142). The following PR for RHEL 7.2's curl fixes this: https://github.com/ktdreyer/curl/pull/1
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. See details at https://github.com/ktdreyer/curl/pull/1
Ceph RGW deadlocks
Ceph RGW does not deadlock
Thanks a lot for identifying the fix and preparing the patches! To summarize it here, this is a request to backport the following upstream commits:
Created attachment 1169974 [details]
beaker regression test for curl_multi_wait
I've attached a beaker regression test to validate the fix.
(In reply to Casey Bodley from comment #5)
> I've attached a beaker regression test to validate the fix.
Works reliably for me. Thank you for preparing the test!
@QE: Please make sure that libcurl-devel is installed for the test to run (unless it is installed somehow automatically).
*** Bug 1367614 has been marked as a duplicate of this bug. ***
Just wondering if there is any chance of getting a copy of the curl-7.29.0-32.el7
packages for testing?
This problems is currently hitting our systems hard with 100% CPU usage on everything. Would like to test this and feed back the info to the DotNet Core team.
Created attachment 1192069 [details]
(In reply to Steven Haigh from comment #13)
> Just wondering if there is any chance of getting a copy of the
> curl-7.29.0-32.el7 packages for testing?
I am attaching an *unsupported* source RPM for *TESTING PURPOSES ONLY*. Please do not use it on production systems. Feedback is appreciated!
Just as an update - I've built these packages and pushed them to my testing repo for testing on the machine with this problem.
I don't want to restart the C# dotnet core app at the moment - but should probably have more info during the work week...
I can confirm that this package fixes the issues we were seeing with the dotnet core applications as per BZ 1367614.
Perfect. Thanks for confirmation!
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.