Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 1203424 - Removing a content host causes gofer ssl errors in /var/log/messages
Removing a content host causes gofer ssl errors in /var/log/messages
Status: CLOSED ERRATA
Product: Red Hat Satellite 6
Classification: Red Hat
Component: Content Management (Show other bugs)
6.1.0
Unspecified Unspecified
unspecified Severity high (vote)
: Beta
: Unused
Assigned To: Jeff Ortel
Corey Welton
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2015-03-18 15:07 EDT by Justin Sherrill
Modified: 2018-09-19 11:21 EDT (History)
9 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2015-08-12 01:30:20 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)


External Trackers
Tracker ID Priority Status Summary Last Updated
Pulp Redmine 758 Normal CLOSED - CURRENTRELEASE Consumer queue delete task does not configure gofer connector Never
Red Hat Product Errata RHSA-2015:1592 normal SHIPPED_LIVE Important: Red Hat Satellite 6.1.1 on RHEL 6 2015-08-12 05:04:35 EDT

  None (edit)
Description Justin Sherrill 2015-03-18 15:07:18 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.
Comment 3 Brian Bouterse 2015-03-19 15:07:03 EDT
The Pulp upstream bug status is at MODIFIED. Updating the external tracker on this bug.
Comment 4 Brian Bouterse 2015-03-19 15:07:04 EDT
The Pulp upstream bug priority is at Normal. Updating the external tracker on this bug.
Comment 5 Brian Bouterse 2015-03-19 16:30:23 EDT
The Pulp upstream bug status is at ON_QA. Updating the external tracker on this bug.
Comment 7 Brian Bouterse 2015-03-20 14:00:22 EDT
The Pulp upstream bug status is at VERIFIED. Updating the external tracker on this bug.
Comment 8 Corey Welton 2015-03-24 20:11:47 EDT
Verified in Satellite-6.1.0-RHEL-7-20150320.1
Comment 9 pulp-infra@redhat.com 2015-04-23 12:39:46 EDT
The Pulp upstream bug status is at CLOSED - CURRENTRELEASE. Updating the external tracker on this bug.
Comment 10 Brian Bouterse 2015-04-29 15:29:17 EDT
Adding mhrivnak@redhat.com to cc list
Comment 11 Brian Bouterse 2015-04-29 15:29:18 EDT
Adding bbouters@redhat.com to cc list
Comment 12 Bryan Kearney 2015-08-11 09:26:04 EDT
This bug is slated to be released with Satellite 6.1.
Comment 13 errata-xmlrpc 2015-08-12 01:30:20 EDT
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

Note You need to log in before you can comment on or make changes to this bug.