Bug 908028 - release upgrade requires that katello-agent must be updated on clients
Summary: release upgrade requires that katello-agent must be updated on clients
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Documentation
Version: 6.0.1
Hardware: Unspecified
OS: Linux
unspecified
medium
Target Milestone: Unspecified
Assignee: Athene Chan
QA Contact: Lana Brindley
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-02-05 17:05 UTC by Brad Buckingham
Modified: 2015-05-11 22:08 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-09-30 04:48:13 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Brad Buckingham 2013-02-05 17:05:51 UTC
Description of problem:

The CFSE 2.0 release will include upgrading to pulp v2.  As a result of that upgrade, clients/consumers that are currently using the katello-agent (which enables administrators to perform various CFSE initiated actions on the client), will need to upgrade the katello-agent on the client to the version distributed with CFSE 2.0.

A couple of alternatives exist for this upgrade:

1. Prior to upgrading the CFSE server, sync the CFSE 2.0 repositories, promote those repositories to the appropriate environments and initiate a server-initiated 'update' on the katello-agent for all clients registered to those environments.  Upon completion of the updates, the CFSE upgrade on the server may be performed.

2. Perform the CFSE upgrade on the server.  Upon completion, sync the CFSE 2.0 repositories, promote those repositories to the appropriate environments and then perform a 'yum update katello-agent' from each of the clients registered to those environments to install the updated package.

For reference, the following are the various server initiated actions that will require this katello-agent upgrade:
- package install/update/remove
- package group install/update/remove
- errata install

Comment 2 Mike McCune 2013-08-16 18:09:14 UTC
getting rid of 6.0.0 version since that doesn't exist


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