Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.
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 1738893

Summary: Updating katello-agent only does not update gofer package
Product: Red Hat Satellite Reporter: Dhaval Joshi <dhjoshi>
Component: katello-agentAssignee: Justin Sherrill <jsherril>
Status: CLOSED ERRATA QA Contact: Radovan Drazny <rdrazny>
Severity: medium Docs Contact:
Priority: medium    
Version: 6.5.0CC: ahumbe, dhjoshi, egolov, jsherril, rdrazny
Target Milestone: 6.6.0Keywords: PrioBumpGSS, Regression, Triaged
Target Release: Unused   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: katello-host-tools-3.5.1-2 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2019-10-22 13:30:45 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 Dhaval Joshi 2019-08-08 11:23:33 UTC
Description of problem:
With the latest version of katello-agent (katello-agent-3.5.0-2) the required version of gofer is only >= 2.12.1

When katello-agent is updated to the latest version, no gofer package was updated. It leads to a situation where, when tried to push updates/erratas via Satelite, it fails. One has to update the gofer package manually and restart the service then it works fine. 

Version-Release number of selected component (if applicable):
6.5.0

How reproducible:
100%

Steps to Reproduce:
1. Use Satellite upgraded from 6.4 to 6.5

2. Update katello-agent
# yum update katello-agent

3. katello-agent will get update to latest => katello-agent-3.5.0.2

$ cat yum_list_installed | grep -i katello
katello-agent.noarch          3.5.0-2.el7sat          @rhel-7-server-satellite-tools-6.5-rpms
katello-host-tools.noarch     3.5.0-2.el7sat          @rhel-7-server-satellite-tools-6.5-rpms

$ cat yum_list_installed | grep -i gofer
gofer.noarch                  2.12.3-1.el7            @rhel-7-server-satellite-tools-6.4-rpms
python-gofer.noarch           2.12.3-1.el7            @rhel-7-server-satellite-tools-6.4-rpms
python-gofer-proton.noarch    2.12.3-1.el7            @rhel-7-server-satellite-tools-6.4-rpms

# rpm -qR katello-agent
/bin/sh
/bin/sh
config(katello-agent) = 3.5.0-2.el7sat
gofer >= 2.12.1 <------------------- Issue
katello-host-tools = 3.5.0-2.el7sat
python(abi) = 2.7 
python-gofer-proton >= 2.5
rpmlib(CompressedFileNames) <= 3.0.4-1
rpmlib(FileDigests) <= 4.6.0-1
rpmlib(PartialHardlinkSets) <= 4.0.4-1
rpmlib(PayloadFilesHavePrefix) <= 4.0-1
subscription-manager
rpmlib(PayloadIsXz) <= 5.2-1

gofer package and its dependencies will not be updated. 

Actual results:
katello-agent package is updated and gofer package is not updated.
This can most likely happen on systems registered on a Satellite that's been updated from 6.4 to 6.5 After publishing the new Satellite Tools for 6.5, If customer only run "yum update katello" on the client, gofer will not be updated if it's higher than version 2.12.1

Expected results:
Gofer package should be updated along with katello-agent.

Additional info:

Comment 4 Radovan Drazny 2019-08-27 12:21:22 UTC
Verified on Sat 6.6 Snap 17. I went through the whole upgrade route for katello-agent starting with Sat 6.4 Tools, upgraded to Sat 6.5 Tools and finally Sat 6.6 Tools, using "yum update katello-agent" only. Sat 6.6 katello-agent pulls in current gofer-2.12.5-5 from Sat 6.6 Tools repo, as it should.

[root@ibm-x3650m4-03-vm12 ~]# yum update katello-agent
<...>
Resolving Dependencies
<...>
Dependencies Resolved

Updating:
 katello-agent                                         noarch      3.5.1-2.el7sat    Default_Organization_Sat66Tools_Sat66ToolsRepo                                    39 k
Updating for dependencies:
 gofer                                                 noarch      2.12.5-5.el7sat   Default_Organization_Sat66Tools_Sat66ToolsRepo                                    52 k
 katello-host-tools                                    noarch      3.5.1-2.el7sat    Default_Organization_Sat66Tools_Sat66ToolsRepo                                    32 k
 python-gofer                                          noarch      2.12.5-5.el7sat   Default_Organization_Sat66Tools_Sat66ToolsRepo                                   194 k
 python-gofer-proton                                   noarch      2.12.5-5.el7sat   Default_Organization_Sat66Tools_Sat66ToolsRepo                                    58 k

<...>

VERIFIED

Comment 6 errata-xmlrpc 2019-10-22 13:30:45 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/RHBA-2019:3175