Bug 1403029

Summary:	Updating katello-agent only does not update dependencies
Product:	Red Hat Satellite	Reporter:	Christian Marineau <cmarinea>
Component:	katello-agent	Assignee:	satellite6-bugs <satellite6-bugs>
Status:	CLOSED ERRATA	QA Contact:	Peter Ondrejka <pondrejk>
Severity:	medium	Docs Contact:
Priority:	high
Version:	6.2.0	CC:	bbuckingham, brcoca, cdonnell, cduryee, gapatil, jcallaha, swadeley
Target Milestone:	Unspecified	Keywords:	PrioBumpGSS, Triaged
Target Release:	Unused
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:	Updating katello-agent did not update dependencies. This is now fixed.	Story Points:	---
Clone Of:		Environment:
Last Closed:	2018-02-21 12:57:01 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:

Description Christian Marineau 2016-12-08 22:55:52 UTC

Description of problem:

With the latest version of katello-agent (katello-agent-2.5.0-5) the required version of gofer is only >= 2.5

This could lead in some situation where the katello-agent is up to date, but not the gofer packages.

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

How reproducible:
100%

Steps to Reproduce:
1. Have a system with the following the following packages
By example:
  - python-gofer-2.6.8-1
  - gofer-2.6.8-1
  - python-gofer-proton-2.6.8-1
  - katello-agent-2.2.6-1

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

3. katello-agent will get update to latest => katello-agent-2.5.0-5
   But gofer package and its dependencies will not be updated. 

Actual results:
Some situation can occurred where katello-agent is at latest version, but the gofer packages are older.

This can most likely happen on systems registered on a Satellite that's been migrated to 6.1.X to 6.2.X. After publishing the new Satellite Tools for 6.2, If customer only run "yum update katello" on the client, gofer will not be updated if it's higher than version 2.5. 

Expected results:
Might adjust dependencies in the next version of katello-agent to ensure gofer is updated as well.

Additional info:
By example, the situation could impact the Errata management from Satellite as the Errata for bug 1323726 is not installed.

Comment 4 Craig Donnelly 2017-01-11 06:30:46 UTC

I think its important to note this is not limited to gofer as a dependency, obviously.

This applies to all dependencies that katello-agent has from the Satellite-Tools repository. (None of them are true deps based on version, one for existing.)

We probably need to start building these SPECS with versions in mind for each errata.

Comment 5 Christian Marineau 2017-01-11 14:11:42 UTC

(In reply to Craig Donnelly from comment #4)
> I think its important to note this is not limited to gofer as a dependency,
> obviously.
> 
> This applies to all dependencies that katello-agent has from the
> Satellite-Tools repository. (None of them are true deps based on version,
> one for existing.)
> 
> We probably need to start building these SPECS with versions in mind for
> each errata.

Thanks this is an very important point that you are bringing.

As a workaround I often do the following:
# yum --disablerepo="*" --enablerepo="rhel-*-server-satellite-tools-6.2-rpms" update

Comment 6 Satellite Program 2017-01-19 15:20:04 UTC

Moving this bug to POST for triage into Satellite 6 since the upstream issue http://projects.theforeman.org/issues/18012 has been resolved.

Comment 7 Craig Donnelly 2017-05-25 18:20:55 UTC

Moving this off of post since the currently attached fix does not address the entire dependency stack.

We need to ensure that when we build a new version of katello-agent for clients that the SPEC included the also latest versions of the defines dependencies:

Requires: gofer >= 2.7.6
Requires: python-gofer-proton >= 2.5
Requires: python-pulp-agent-lib >= 2.6
Requires: pulp-rpm-handlers >= 2.6

These should be updated to what is shipping in satellite-tools with the latest available version to enforce that customers get full updates.

Is there any reason this isn't an acceptable answer?

Comment 8 Satellite Program 2017-05-25 20:02:34 UTC

Moving this bug to POST for triage into Satellite 6 since the upstream issue http://projects.theforeman.org/issues/18012 has been resolved.

Comment 13 errata-xmlrpc 2018-02-21 12:57:01 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-2018:0338