Bug 1536843

Summary:	self registered satellite update steps are incorrect
Product:	Red Hat Satellite	Reporter:	Ian Tewksbury <itewksbu>
Component:	Docs Install Guide	Assignee:	Vlada Grosu <vgrosu>
Status:	CLOSED CURRENTRELEASE	QA Contact:	csherrar
Severity:	medium	Docs Contact:
Priority:	medium
Version:	6.2.13	CC:	adahms, brubisch, itewksbu, swadeley
Target Milestone:	Unspecified
Target Release:	Unused
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2018-01-23 15:56:29 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:
Bug Blocks:	1363814

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.