Bug 1330860 - 6.1 katello-agent does not work with 6.2 Sat? Would clients stop working if only Sat is upgraded?
Summary: 6.1 katello-agent does not work with 6.2 Sat? Would clients stop working if o...
Keywords:
Status: CLOSED WORKSFORME
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: katello-agent
Version: 6.2.0
Hardware: Unspecified
OS: Unspecified
unspecified
high vote
Target Milestone: Unspecified
Assignee: satellite6-bugs
QA Contact: Katello QA List
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-04-27 07:13 UTC by Jan Hutař
Modified: 2019-04-01 20:27 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-05-11 16:19:59 UTC
Target Upstream Version:


Attachments (Terms of Use)

Description Jan Hutař 2016-04-27 07:13:11 UTC
Description of problem:
6.1 katello-agent+gofer package versions does not work with 6.2 Sat? Would clients stop working if only Sat is upgraded?


Version-Release number of selected component (if applicable):
Client: katello-agent-1.5.3-7.el7sat.noarch
        gofer-1.3.0-1.el7sat.noarch
Sat: satellite-6.2.0-8.2.beta.el7sat.noarch


How reproducible:
always


Steps to Reproduce:
1. Install 6.1 katello-agent to client (content host) registered to 6.2 Sat
2. Schedule some errata update for that content host on Satellite webUI


Actual results:
Content hosts did not pick the event, Sat's webUI says, that task failed because:

  Host did not respond within 20 seconds. The task has been cancelled. Is katello-agent installed and goferd running on the Host?


Expected results:
Should work


Additional info:
Maybe this is not supported combination, but reporting this because we have to be sure to catch customer scenarios like:

1. Customer have 1000 content hosts with 6.1 katello-agent and Sat 6.1, all
   works for him
2. Customer updates Satellite to 6.2
3. Customer notices that he can not update its clients using katello-agent now
   (so he can not upgrade katello-agent+goferd on them)

NOTE: I have not tested above scenario exactly (I was not upgrading Satellite), so maybe it would work. Filling this anyway to be pretty sure as IMO this can cause problems to customers.

When I have upgraded katello-agent + gofer + deps. and restarted goferd, it started to work.

Comment 2 Mike McCune 2016-05-11 16:19:59 UTC
Can you verify that your firewall is configured correctly?

I did the following:

1) Satellite 6.2 Beta Server
2) Client with 6.1 gofer and katello-agent:

# rpm -q katello-agent gofer
katello-agent-2.2.6-1.el7sat.noarch
gofer-2.6.8-1.el7sat.noarch

3) connected fine to the Satellite:

May 11 16:14:20 mmccune-nohg-media goferd: [INFO][worker-0] gofer.messaging.adapter.proton.connection:103 - connected: amqps://sat-r220-06.lab.eng.rdu2.redhat.com:5647
May 11 16:14:20 mmccune-nohg-media goferd: [INFO][worker-0] root:507 - connected to sat-r220-06.lab.eng.rdu2.redhat.com:5647

4) Installed a package via the webUI:

Action Type Install package
User admin
Started At 5/11/16 9:14 AM
Finished At 5/11/16 9:14 AM
Parameters zsh
State stopped
Result success
Details

zsh-5.0.2-14.el7.x86_64


5) Installed errata updates via the webUI:

Action Type Install erratum
User admin
Started At 5/11/16 9:15 AM
Finished At 5/11/16 9:15 AM
Parameters RHBA-2016:0545, RHBA-2016:0181
State stopped
Result success
Details

tuned-2.5.1-4.el7_2.3.noarch
systemd-libs-219-19.el7_2.7.x86_64
systemd-sysv-219-19.el7_2.7.x86_64
systemd-219-19.el7_2.7.x86_64
libgudev1-219-19.el7_2.7.x86_64

We did not make any large changes between 6.1 -> 6.2 that would force an incompatibility 

I'm going to close this out as WORKSFORME but feel free to re-open if you verify all firewall settings are opened correctly between client -> satellite and you still can't get this working.

If you have an environment we can SSH into to investigate at that point, feel free to share.


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