Since the problem described in this issue should be resolved in a recent advisory, it has been closed.

For information on the advisory (Critical: Satellite 6.16.0 release), and where to find the updated files, follow the link below.

If the solution does not work for you, open a new bug report.
https://access.redhat.com/errata/RHSA-2024:8906

Upon review of our valid but aging backlog the Satellite Team has concluded that this Jira does not meet the criteria for a resolution in the near term, and are planning to close in a month. This message may be a repeat of a previous update and the bug is again being considered to be closed. If you have any concerns about this, please contact your Red Hat Account team. Thank you.

This BZ has been automatically migrated to the issues.redhat.com Red Hat Issue Tracker. All future work related to this report will be managed there.

Due to differences in account names between systems, some fields were not replicated. Be sure to add yourself to Jira issue's "Watchers" field to continue receiving updates and add others to the "Need Info From" field to continue requesting information.

To find the migrated issue, look in the "Links" section for a direct link to the new issue location. The issue key will have an icon of 2 footprints next to it, and begin with "SAT-" followed by an integer. You can also find this issue by visiting https://issues.redhat.com/issues/?jql= and searching the "Bugzilla Bug" field for this BZ's number, e.g. a search like:

"Bugzilla Bug" = 1234567

In the event you have trouble locating or viewing this issue, you can file an issue by sending mail to rh-issues@redhat.com. You can also visit https://access.redhat.com/articles/7032570 for general account information.

Hi Eric, documentation still contains explicit steps for module enable "dnf module enable satellite-maintenance:el8" and maintenance repo enable "subscription-manager repos --enable satellite-maintenance-6.14-for-rhel-8-x86_64-rpms", which could be done as part of "satellite-maintain self-upgrade" command itself for y-stream upgrades, so shouldn't we document it instead?

Also, we are recommending self-upgrade in Capsule upgrade guide, and its missing in Satellite upgrade guide, which is inconsistent as of now, so I don't think this should be closed as NOTABUG here, I would like to hear your opinion on this,
https://access.redhat.com/documentation/en-us/red_hat_satellite/6.14/html/upgrading_red_hat_satellite_to_6.14/upgrading_satellite#upgrading_capsule_server_upgrade-guide

Hello Gaurav,

Many thanks for reporting this issue.

The BZ has been assigned and the docs team will keep informing about any progress on the fix in this ticket.

Thank you!