Bug 1180692
| Summary: | use of rh-common repos for katello-agent & hammer means 6.0 users will get updates | ||
|---|---|---|---|
| Product: | Red Hat Satellite | Reporter: | Justin Sherrill <jsherril> |
| Component: | katello-agent | Assignee: | Katello Bug Bin <katello-bugs> |
| Status: | CLOSED CURRENTRELEASE | QA Contact: | Tazim Kolhar <tkolhar> |
| Severity: | high | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 6.0.4 | CC: | bbuckingham, bkearney, chrobert, cperry, cwelton, jsherril, tkolhar |
| Target Milestone: | Unspecified | Keywords: | Triaged |
| 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-08-12 13:55:23 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: | |||
| Bug Depends On: | 1205668 | ||
| Bug Blocks: | |||
|
Description
Justin Sherrill
2015-01-09 17:35:19 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. QE note: not tons to test here, though it is an upgrade consideration. hi please provide verification steps thanks 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 upgrade is failing for now due to https://bugzilla.redhat.com/show_bug.cgi?id=1215563 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 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 This bug is slated to be released with Satellite 6.1. This bug was fixed in version 6.1.1 of Satellite which was released on 12 August, 2015. |