Bug 1218988

Summary: While upgrading katello agent, gofer service throws an error messages of disconnection.
Product: Red Hat Satellite Reporter: Jitendra Yejare <jyejare>
Component: katello-agentAssignee: Katello Bug Bin <katello-bugs>
Status: CLOSED DUPLICATE QA Contact: Katello QA List <katello-qa-list>
Severity: high Docs Contact:
Priority: unspecified    
Version: 6.1.0CC: agk, ritaro4278, sghai
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-05-06 13:56:22 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:
Attachments:
Description Flags
Gofer service status logs and /var/log/messages on host system. none

Description Jitendra Yejare 2015-05-06 11:10:35 UTC
Created attachment 1022598 [details]
Gofer service status logs and /var/log/messages on host system.

Description of problem:
While upgrading a katello agent on Host, Gofer service throws an Error messages of disconnection: "[ERROR][worker-0] gofer.messaging.adapter.proton.connection:106 - connect: proton+amqps://sat6-qe-rhel7.usersys.redhat.com:564...disconnected".
Also same error messages can be observed under /var/log/messages.

Version-Release number of selected component (if applicable):
katello-agent-1.5.3-7.el7sat.noarch - Before upgrade
katello-agent-2.2.3-1.el7sat.noarch - After Upgrade

How reproducible:

Pre-requisites:
Satellite 6.0.8 with at-least one content host registered.

Steps to Reproduce:
1. Sync Sat6 tools repo in above satellite..
2. Update the CV, add sat6 repos.
3. Publish and promote the CV.
4. Update an activation key by adding the sat 6 tools repo.
5. Refresh Subscription-manager on host machine.
6. Run 'yum update -y katello-agent'.

Actual results:
Update shoes Success but gofer service throws an error messages in /var/log/messages and also in service gofer status.
PFA the logs of /var/log/messages and 'service gofer status' command.

Expected results:
Gofer should not throw error messages.

Additional info:

Comment 2 Jitendra Yejare 2015-05-06 13:56:22 UTC

*** This bug has been marked as a duplicate of bug 1217828 ***