Bug 2217515

Summary:	foreman-maintain self-upgrade doesn't enable the right repository before enabling the module
Product:	Red Hat Satellite	Reporter:	Direct Docs Feedback <ddf-bot>
Component:	Foreman Maintain	Assignee:	satellite6-bugs <satellite6-bugs>
Status:	NEW ---	QA Contact:	Satellite QE Team <sat-qe-bz-list>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	6.13.0	CC:	agadhave, egolov, mjivraja
Target Milestone:	Unspecified	Keywords:	Triaged
Target Release:	Unused
Hardware:	All
OS:	All
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:		Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Direct Docs Feedback 2023-06-26 13:53:56 UTC

I think it might be helpful to have the actual command to make that repo available.

subscription-manager repos --enable satellite-maintenance-6.13-for-rhel-8-x86_64-rpms

Thank you.

Reported by: rhit_jbittner

https://access.redhat.com/documentation/en-us/red_hat_satellite/6.13/html/upgrading_and_updating_red_hat_satellite/upgrading_satellite#annotations:eb79d64d-8030-4661-9f97-132dfe783138

Comment 2 Marie Hornickova 2023-06-27 16:22:01 UTC

Hello, 
Many thanks for using the Direct documentation Feedback tool to report this issue.
The Bugzilla will go through proper team triage, and the documentation team will use this ticket toinform about updates on the implementation to product documentation.
Thank you!

Comment 3 Evgeni Golov 2023-06-29 12:49:19 UTC

instead of documenting "one needs to enable the repo", f-m actually has code to do so, but fails to enable the module *if* the repo was not enabled *before* the run (and if the module is not enabled, the upgrade won't do much)