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 1536843 - self registered satellite update steps are incorrect
Summary: self registered satellite update steps are incorrect
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Docs Install Guide
Version: 6.2.13
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: Unspecified
Assignee: Vlada Grosu
QA Contact: csherrar
URL:
Whiteboard:
Depends On:
Blocks: 1363814
TreeView+ depends on / blocked
 
Reported: 2018-01-21 16:06 UTC by Ian Tewksbury
Modified: 2021-03-11 16:59 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-01-23 15:56:29 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Description Ian Tewksbury 2018-01-21 16:06:03 UTC 
Document URL: 
https://access.redhat.com/documentation/en-us/red_hat_satellite/6.2/html-single/installation_guide/#updating_satellite_server_to_next_minor_version

https://access.redhat.com/documentation/en-us/red_hat_satellite/6.2/html-single/installation_guide/#updating_satellite_server_to_next_minor_version

Section Number and Name: 

7.1 Updating Satellite server
7.2 Updating Capsule Server


Describe the issue: 

As per https://access.redhat.com/solutions/3222091 the instructions as documented for updating a self registered satellite no longer work.  As per https://bugzilla.redhat.com/show_bug.cgi?id=1505286 the underlying technical issue can not be "fixed".

The documentation should be updated to reflect the new steps otherwise everyone is going to run into this bug and then spend hours searching until they finally find that access article.


Suggestions for improvement: 

Update step "3. Update all packages" to be `yum -y update --cache --disableplugin=enabled_repos_upload --disableplugin=package_upload --disableplugin=subscription-manager` as per https://access.redhat.com/solutions/3222091
Comment 1 Andrew Dahms 2018-01-22 05:49:20 UTC 
Assigning to Vlada for review.

Vlada - this looks like a change that only affects 6.2.
Comment 2 Vlada Grosu 2018-01-23 09:30:57 UTC 
Hi Ian Tewksburry,

Can you please confirm that the update command needs to be updated for the "Updating Capsule Server" topic as well?
The solution only mentions that it is applicable for a self-registered Satellite upgrade.(https://access.redhat.com/solutions/3222091)

Many thanks,
Vlada
Comment 4 Stephen Wadeley 2018-01-23 10:18:25 UTC 
(In reply to Vlada Grosu from comment #2)
> Hi Ian Tewksburry,
> 
> Can you please confirm that the update command needs to be updated for the
> "Updating Capsule Server" topic as well?
> The solution only mentions that it is applicable for a self-registered
> Satellite upgrade.(https://access.redhat.com/solutions/3222091)
> 
> Many thanks,
> Vlada

Hello Vlada

The commands in comment 0 only apply to updating a self-registered Satellite (because you have to stop the Satellite application while updating the packages, but its the Satellite that has the packages you need, so you have to download them first in this way).

This does not apply to Capsules because they are registered to the Satellite, not themselves.

Thank you
Comment 5 Vlada Grosu 2018-01-23 10:23:06 UTC 
(In reply to Stephen Wadeley from comment #4)

> Hello Vlada
> 
> The commands in comment 0 only apply to updating a self-registered Satellite
> (because you have to stop the Satellite application while updating the
> packages, but its the Satellite that has the packages you need, so you have
> to download them first in this way).
> 
> This does not apply to Capsules because they are registered to the
> Satellite, not themselves.
> 
> Thank you

Thank you, Stephen.
It makes more sense now.

Kind regards,
Vlada
Comment 10 Ian Tewksbury 2018-02-02 14:01:21 UTC 
Thank you Vlada and Cliften, very much appreciated.
Note You need to log in before you can comment on or make changes to this bug.