Red Hat Satellite engineering is moving the tracking of its product development work on Satellite to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "Satellite project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs will be migrated starting at the end of May. If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "Satellite project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/SAT-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 1115988 - qpidd produces errors in /var/log/messages when previously subscribed clients are left pointing at a rebuilt host
Summary: qpidd produces errors in /var/log/messages when previously subscribed clients...
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Other
Version: 6.0.3
Hardware: x86_64
OS: Linux
unspecified
high
Target Milestone: Unspecified
Assignee: satellite6-bugs
QA Contact: Katello QA List
URL:
Whiteboard:
: 1154559 (view as bug list)
Depends On:
Blocks: 1122832
TreeView+ depends on / blocked
 
Reported: 2014-07-03 13:10 UTC by Roy Williams
Modified: 2019-04-01 20:27 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-08-11 12:12:38 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Description Roy Williams 2014-07-03 13:10:41 UTC 
Description of problem:
A barrage of errors occur when client machines that were registered to a hostname, for example engr-lbs.uncc.edu, then that host is rebuilt causing it to have new certificates that differ from what the clients were originally registered with to engr-lbs.uncc.edu. This will cause "pulp: kombu.transport.qpid:ERROR: connection aborted" errors to appear in rapid succession approximately every minute, and causes other issues to occur like dynflow becoming stuck at planned state.


Version-Release number of selected component (if applicable):
qpid-cpp-server 0.22-42.el6
qpid-cpp-client 0.22-42.el6
pulp 2.4.0-0.23.beta.el6sat
katello 1.5.0-26.el6sat

How reproducible:
Easily

Steps to Reproduce:
1.  Install RHEL 6.5
2.  Subscribe and Register host via Subscription-Manager, add Red Hat Satellite Beta Entitlement.
3.  Run: yum update -y
4.  Run: subscription-manager repos --enable=rhel-6-server-rpms --enable=rhel-server-rhscl-6-rpms --enable=rhel-server-6-satellite-6-beta-rpms
5.  Run: yum install katello
6.  Run: katello-installer
7.  Run: service iptables stop
8.  Register a client host or several to the satellite 6.0 beta host. I had 15 registered to mine previously, these were RHEL 7.0 GA desktops.
9.  Repeat steps 1-7 on the same host, ie completely rebuilding the host. 

Actual results:
You will see "pulp: kombu.transport.qpid:ERROR: connection aborted" occurring related to the total number of host that were formerly registered at the machine. Host will actually exhibit other problems once this has started like being unable to execute tasks that are created and get stuck in planned phase. 

Expected results:
It shouldn't produce a barrage of "pulp: kombu.transport.qpid:ERROR: connection aborted" errors. The output should be useful instead of vague, since those errors were related to authentication failures. Katello should be able to continue executing tasks.

Additional info:
Comment 1 RHEL Program Management 2014-07-03 13:27:26 UTC 
Since this issue was entered in Red Hat Bugzilla, the release flag has been
set to ? to ensure that it is properly evaluated for this release.
Comment 3 Roy Williams 2014-07-03 13:30:39 UTC 
Another error that occurs post installation before things start getting crazy with the kombu.tarnsport.qpid issue.

"qpidd[46470]: 2014-07-03 09:24:55 [System] error Error reading socket: Success(0)"
Comment 4 Roy Williams 2014-07-09 20:56:31 UTC 
I can temporarily resolve the issue via:
Changing the firewall to block port 5671/tcp then running: 
foreman-rake jobs:clear

This seems to let Satellite recover from the issue, as long as those host remain blocked.
Comment 5 Roy Williams 2014-07-15 14:27:50 UTC 
To add the clients are registered via rhsm and goferd.
Comment 6 Peter Vreman 2015-02-23 16:03:39 UTC 
I am having the same issue after rebuilding the Sat6 server. Issue still occurs with Sat6 6.0.7

# grep -c 'qpidd.*error Error reading socket.*Success' /var/log/messages
52837
Comment 7 Peter Vreman 2016-03-08 14:19:35 UTC 
*** Bug 1154559 has been marked as a duplicate of this bug. ***
Comment 11 Bryan Kearney 2016-08-04 20:10:10 UTC 
Moving 6.2 bugs out to sat-backlog.
Comment 13 Peter Vreman 2017-08-08 11:23:38 UTC 
I think this can be closed with the fix of https://bugzilla.redhat.com/show_bug.cgi?id=1445403 that removes the need for goferd on the clients
Comment 14 Bryan Kearney 2017-08-11 12:12:38 UTC 
Closing based on Peters comments in 13.
Note You need to log in before you can comment on or make changes to this bug.