Description of problem: Customer has indicated they would like to see a better method for determining if there is a networking infrastructure issue or if the issue does indeed reside in Ceph application. For example customer had a large Ceph cluster with millions of objects that were continuously being added. During the process they would have OSDs that would hang. Initial findings from engineering indicated this was probably a networking issue however when they reduced the number of objects the hang behaviour went away and/or was reduced thus proving the networking infrastructure was sound. Having a method to better identify Ceph related issues or external related infrastructure issues would help to focus where troubleshooting should continue in a complex case. Version-Release number of selected component (if applicable): 2.4 How reproducible: NA Steps to Reproduce: 1. 2. 3. Actual results: NA Expected results: NA Additional info:
Updating the QA Contact to a Hemant. Hemant will be rerouting them to the appropriate QE Associate. Regards, Giri
This is in all 5.0 builds - needs qa ack.
Not sure why the bot didn't change this, but it has all acks and is in all build, so it should be ON_QA