This may be related to this bug:
which we can deliver a hotfix to anyone interested
We've attempted a few fixes with select pulp users, but have not solved it. We are actively working on it. (QPID-7317)
*** Bug 1388814 has been marked as a duplicate of this bug. ***
Retitling to describe the symptoms more accurately
@igreen, I agree that this issue does not sound like the root cause of your case. Since we both think it's not the root cause, I am going to remove the association from case 01681610. If I am incorrect in that, please let me know or re-add it.
Even though that case was the one that started this BZ, we had been investigating this issue in upstream Pulp already.
*** HOTFIX INSTRUCTIONS ***
Before restarting services make sure all sync/pulp tasks are finished
# wget http://people.redhat.com/chrobert/hf1377195/python-qpid-0.30-11.el7sat.noarch.rpm
# yum localupdate python-qpid-0.30-11.el7sat.noarch.rpm
# katello-service restart
# wget http://people.redhat.com/chrobert/hf1377195/python-qpid-0.30-11.el6sat.noarch.rpm
# yum localupdate python-qpid-0.30-11.el6sat.noarch.rpm
# katello-service restart
After this is done resume normal operations. Tested on ref7 (6.2.8) with the el7 steps and worked fine to update.
I agree w/ @mhrivnak's reading of that exception. It is not related to the deadlocking (which is good) and that it's an SSL trust issue when trying to publish results to Katello.
This was discussed to be included with 6.2.9 if possible. I'm setting that as the target milestone. To include, bring in the one package in Comment 29. https://bugzilla.redhat.com/show_bug.cgi?id=1377195#c29
Confirming that it is fixed is difficult because we don't know how to trigger it and it occurs rarely. I would like QE to ensure that no new regressions are introduced with this change using normal regression testing. A few basic sync/publish actions in sat6 should do it.
Verified in Satellite 6.2.9 Snap 3.
Based on no-break criteria as well as reports from customer environments, this issue is fixed in the version above.
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.
This BZ was about a root cause that is very difficult to reproduce. If you can reproduce a defect regularly with similar symptoms please file a new bug because you have a different root cause then.