Red Hat Bugzilla – Bug 1203424
Removing a content host causes gofer ssl errors in /var/log/messages
Last modified: 2018-09-19 11:21:45 EDT
Description of problem: After I noticing gofer ssl errors in /var/log/messages, jortel discovered that a queue cleanup task that occurs whenever a consumer is deleted did not have the correct configuration. How reproducible: Always Steps to Reproduce: 1. Install sat 6.1 2. Register a content host 3. unregister/remove the content host 4. Wait 10 minutes 5. Monitor /var/log/messages Actual results: SSL Errors spewing in /var/log/messages related to gofer: Mar 18 15:04:11 rhsm-qe-2 qpidd: 2015-03-18 15:04:11 [System] error Error reading socket: Success(0) Mar 18 15:04:11 rhsm-qe-2 qpidd[9677]: 2015-03-18 15:04:11 [System] error Error reading socket: Success(0) Mar 18 15:04:11 rhsm-qe-2 pulp: gofer.messaging.adapter.qpid.connection:ERROR: connect: qpid+ssl://rhsm-qe-2.rhq.lab.eng.bos.redhat.com:5671, failed: [Errno 1] _ssl.c:504: error:14094412:SSL routines:SSL3_READ_BYTES:sslv3 alert bad certificate Mar 18 15:04:11 rhsm-qe-2 pulp: gofer.messaging.adapter.qpid.connection:INFO: retry in 106 secon Expected results: No errors Additional info: This is related to a 'cleanup' task in pulp to cleanup the consumer qeueue. It *shouldn't* affect any other functionality other than queue cleanup.
The Pulp upstream bug status is at MODIFIED. Updating the external tracker on this bug.
The Pulp upstream bug priority is at Normal. Updating the external tracker on this bug.
The Pulp upstream bug status is at ON_QA. Updating the external tracker on this bug.
The Pulp upstream bug status is at VERIFIED. Updating the external tracker on this bug.
Verified in Satellite-6.1.0-RHEL-7-20150320.1
The Pulp upstream bug status is at CLOSED - CURRENTRELEASE. Updating the external tracker on this bug.
Adding mhrivnak@redhat.com to cc list
Adding bbouters@redhat.com to cc list
This bug is slated to be released with Satellite 6.1.
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. https://access.redhat.com/errata/RHSA-2015:1592