Bug 1203424

Summary:	Removing a content host causes gofer ssl errors in /var/log/messages
Product:	Red Hat Satellite	Reporter:	Justin Sherrill <jsherril>
Component:	Content Management	Assignee:	Jeff Ortel <jortel>
Status:	CLOSED ERRATA	QA Contact:	Corey Welton <cwelton>
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	6.1.0	CC:	bmbouter, cwelton, daviddavis, dkliban, ggainey, ipanova, jmontleo, mhrivnak, mmccune, pcreech, rchan, ttereshc
Target Milestone:	Unspecified
Target Release:	Unused
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2015-08-12 05:30:20 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Justin Sherrill 2015-03-18 19:07:18 UTC

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.

Comment 3 Brian Bouterse 2015-03-19 19:07:03 UTC

The Pulp upstream bug status is at MODIFIED. Updating the external tracker on this bug.

Comment 4 Brian Bouterse 2015-03-19 19:07:04 UTC

The Pulp upstream bug priority is at Normal. Updating the external tracker on this bug.

Comment 5 Brian Bouterse 2015-03-19 20:30:23 UTC

The Pulp upstream bug status is at ON_QA. Updating the external tracker on this bug.

Comment 7 Brian Bouterse 2015-03-20 18:00:22 UTC

The Pulp upstream bug status is at VERIFIED. Updating the external tracker on this bug.

Comment 8 Corey Welton 2015-03-25 00:11:47 UTC

Verified in Satellite-6.1.0-RHEL-7-20150320.1

Comment 9 pulp-infra@redhat.com 2015-04-23 16:39:46 UTC

The Pulp upstream bug status is at CLOSED - CURRENTRELEASE. Updating the external tracker on this bug.

Comment 10 Brian Bouterse 2015-04-29 19:29:17 UTC

Adding mhrivnak to cc list

Comment 11 Brian Bouterse 2015-04-29 19:29:18 UTC

Adding bbouters to cc list

Comment 12 Bryan Kearney 2015-08-11 13:26:04 UTC

This bug is slated to be released with Satellite 6.1.

Comment 13 errata-xmlrpc 2015-08-12 05:30:20 UTC

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