Bug 1767134

Summary:	Update upgrade guide to specify to update gofer separately
Product:	Red Hat Satellite	Reporter:	Melanie Corr <mcorr>
Component:	Documentation	Assignee:	Melanie Corr <mcorr>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Sergei Petrosian <spetrosi>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	6.6.0	CC:	greartes, swadeley, wpinheir
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:	2019-11-05 08:29:37 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:

Description Melanie Corr 2019-10-30 18:28:04 UTC

Document URL: https://access.redhat.com/documentation/en-us/red_hat_satellite/6.4/html/upgrading_and_updating_red_hat_satellite/upgrading_puppet-1#upgrading_satellite_hosts_to_puppet_5

Section Number and Name: 4.3. Upgrading Satellite Hosts to Puppet 5

Describe the issue: There is a bug at the moment that means updating katello-agent pulls in gofer, which then corrupts the process of updating

Suggestions for improvement: Add to the docs to update gofer first so that it does not get corrupted by yum update until the bug is resolved. 

Additional information: 

https://access.redhat.com/solutions/3724271

https://bugzilla.redhat.com/show_bug.cgi?id=1653040

Comment 1 Melanie Corr 2019-11-01 14:12:40 UTC

I have a draft doc ready for publication but have asked a question on the mailing list and am waiting response.

Comment 7 Melanie Corr 2019-11-05 08:29:37 UTC

These changes are now live on the Customer Portal: 

Document URL: https://access.redhat.com/documentation/en-us/red_hat_satellite/6.4/html/upgrading_and_updating_red_hat_satellite/upgrading_puppet-1#upgrading_satellite_hosts_to_puppet_5


Thanks, 

Melanie