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 1180692 - use of rh-common repos for katello-agent & hammer means 6.0 users will get updates
Summary: use of rh-common repos for katello-agent & hammer means 6.0 users will get up...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: katello-agent
Version: 6.0.4
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: Unspecified
Assignee: Katello Bug Bin
QA Contact: Tazim Kolhar
URL:
Whiteboard:
Depends On: 1205668
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-01-09 17:35 UTC by Justin Sherrill
Modified: 2017-02-23 20:39 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-08-12 13:55:23 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Description Justin Sherrill 2015-01-09 17:35:19 UTC 
Description of problem:

Since Satellite 6.0 just has all its updates in rh-common, this means that all Satellite 6.0 users will start receiving updating katello-agent and hammer packages when 6.1 is released.  I do not believe that it is assumed for katello-agent or hammer to be backwards compatible.   So there may be some breakages or awkwardness. 


How reproducible:
always

Steps to Reproduce:
1.  Invent a time machine
2.  Travel to the future when 6.1 is released and the client utilities have been released into the rh-common repos
3.  Update a client pointed to rh-common

Actual results:

Satellite 6.0 users have their clients updated to 6.1 packages which may or may not work.


Expected results:

Satellite 6.0 users have clients that do work and ideally are 6.0 packages


Additional info:
Comment 3 Justin Sherrill 2015-01-12 18:14:10 UTC 
It is handled similarly to the rh-common repo with a few stipulations (cc'ing cliff to correct where I'm wrong):


* The agent utilities (rhncfg, osad) were typically tested for backwards compatibility.  A client upgrading to the newest packages still work with the older satellite.  Cliff, how much qa goes into client verification?

* There was no cli to worry about it (although a cli will be added in 5.7)

For satellite 6:

* the new agent may work with the older satellite (or it may not), this could be a QA task.  (Depending on how the qpid proxying through the capsule work goes, the answer to this may change as well).
* Due to the way that hammer cli interacts with apipie, I do not believe we can say that it will work with the older satellite.  Issues like this: http://projects.theforeman.org/issues/8913 make me think so.
Comment 6 Corey Welton 2015-02-20 16:46:34 UTC 
QE note: not tons to test here, though it is an upgrade consideration.
Comment 8 Tazim Kolhar 2015-04-21 10:09:19 UTC 
hi

please provide verification steps

thanks
Comment 9 Justin Sherrill 2015-04-21 11:35:54 UTC 
To verify this bz, you may need to wait for upgrade testing:

1.  Install a client for a 6.0 satellite, it should be using the rh-common repo
2.  Upgrade the Satellite to 6.1
3.  Attempt to upgrade that client for use on Satellite 6.1.
4.  This should require you to enable the 6.1 tools repo on the satellite, sync it, get it into the client's content view (if needed), enable that repo on the client, and yum update katello-agent

It should not simply get the new packages from rh-common
Comment 10 Tazim Kolhar 2015-04-27 09:53:55 UTC 
upgrade is failing for now due to

https://bugzilla.redhat.com/show_bug.cgi?id=1215563
Comment 11 Tazim Kolhar 2015-05-05 08:56:51 UTC 
Katello upgrade is failing


# katello-installer --upgrade
File not found /usr/share/katello-installer/modules/katello_plugin_gutterball/manifests/init.pp, check your answer file
Comment 12 Tazim Kolhar 2015-05-18 11:32:55 UTC 
VERIFIED:
# rpm -qa | grep foreman
rubygem-hammer_cli_foreman_docker-0.0.3.6-1.el6_6sat.noarch
foreman-vmware-1.7.2.21-1.el6_6sat.noarch
ruby193-rubygem-foreman_docker-1.2.0.12-1.el6_6sat.noarch
rubygem-hammer_cli_foreman-0.1.4.11-1.el6_6sat.noarch
foreman-ovirt-1.7.2.21-1.el6_6sat.noarch
ruby193-rubygem-foreman_hooks-0.3.7-2.el6_6sat.noarch
ibm-ls22-01.rhts.eng.brq.redhat.com-foreman-proxy-1.0-1.noarch
rubygem-hammer_cli_foreman_discovery-0.0.1.10-1.el6_6sat.noarch
foreman-libvirt-1.7.2.21-1.el6_6sat.noarch
ruby193-rubygem-foreman-redhat_access-0.1.0-1.el6_6sat.noarch
ruby193-rubygem-foreman-tasks-0.6.12.5-1.el6_6sat.noarch
ruby193-rubygem-foreman_gutterball-0.0.1.9-1.el6_6sat.noarch
ibm-ls22-01.rhts.eng.brq.redhat.com-foreman-proxy-client-1.0-1.noarch
rubygem-hammer_cli_foreman_tasks-0.0.3.4-1.el6_6sat.noarch
foreman-1.7.2.21-1.el6_6sat.noarch
foreman-gce-1.7.2.21-1.el6_6sat.noarch
ruby193-rubygem-foreman_bootdisk-4.0.2.13-1.el6_6sat.noarch
foreman-proxy-1.7.2.4-1.el6_6sat.noarch
rubygem-hammer_cli_foreman_bootdisk-0.1.2.7-1.el6_6sat.noarch
foreman-selinux-1.7.2.13-1.el6_6sat.noarch
foreman-compute-1.7.2.21-1.el6_6sat.noarch
ibm-ls22-01.rhts.eng.brq.redhat.com-foreman-client-1.0-1.noarch
ruby193-rubygem-foreman_discovery-2.0.0.13-1.el6_6sat.noarch
foreman-postgresql-1.7.2.21-1.el6_6sat.noarch
foreman-debug-1.7.2.21-1.el6_6sat.noarch

steps:
1.  Install a client for a 6.0 satellite, it should be using the rh-common repo
2.  Upgrade the Satellite to 6.1
3.  Attempt to upgrade that client for use on Satellite 6.1.
4.  This should require you to enable the 6.1 tools repo on the satellite, sync it, get it into the client's content view (if needed), enable that repo on the client, and yum update katello-agent

#  katello-installer --upgrade
Upgrading...
Upgrade Step: stop_services...
Upgrade Step: start_mongo...
Upgrade Step: migrate_pulp...
Upgrade Step: migrate_candlepin...
Upgrade Step: migrate_foreman...
Upgrade Step: Running installer...
Installing             Info: START 622                                    [0%]                                             [100%] []
  The full log is at /var/log/katello-installer/katello-installer.log
Upgrade Step: Restarting services...
Upgrade Step: db:seed...
Upgrade Step: Running errata import task (this may take a while)...
Katello upgrade completed!

# rpm -qa |  grep katello-agent
katello-agent-2.2.3-1.el6_6sat.noarch

# yum update katello-agent
Loaded plugins: package_upload, product-id, security, subscription-manager
Setting up Update Process
No Packages marked for Update
Comment 13 Bryan Kearney 2015-08-11 13:18:23 UTC 
This bug is slated to be released with Satellite 6.1.
Comment 14 Bryan Kearney 2015-08-12 13:55:23 UTC 
This bug was fixed in version 6.1.1 of Satellite which was released on 12 August, 2015.
Note You need to log in before you can comment on or make changes to this bug.