Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
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.
Document URL: https://access.redhat.com/documentation/en-us/red_hat_satellite/6.8-beta/html/upgrading_and_updating_red_hat_satellite/
Section Number and Name: 3.1.1 and
Describe the issue: Steps 5, 7, 8, and 10 are missing steps
Suggestions for improvement:
Step 5: Change the repository enablement command to:
subscription-manager repos --enable rhel-7-server-satellite-maintenance-6-beta-rpms --enable rhel-7-server-satellite-6-beta-rpms --enable rhel-7-server-ansible-2.9-rpms
Step 7, 8, and 10: Add this to the command:
FOREMAN_MAINTAIN_USE_BETA=1 <existing command>
Additional information:
Hello Glen,
thank you for raising this bug. Adding FOREMAN_MAINTAIN_USE_BETA=1 to steps that use `satellite-maintain upgrade` is being processed in BZ#1877397. I will investigate about the repositories.
Hi Amit,
Currently, our docs tell users to enable only the rhel-7-server-satellite-maintenance-6-beta-rpms repository prior to upgrade.
This bug suggest enabling rhel-7-server-satellite-6-beta-rpms and rhel-7-server-ansible-2.9-rpms too. My understanding was that satellite-maintain takes care of required repositories and enables them automatically when you run `satellite-maintain upgrade run --target-version 6.8-beta`, therefore you only need to enable rhel-7-server-satellite-maintenance-6-beta-rpms to obtain the latest version of the satellite-maintain package. Is that correct?
Thank you
It has been proven that you only need to have the rhel-7-server-satellite-maintenance-6-beta-rpms repository enabled to be able to get the latest satellite-maintain version. Then, satellite-maintain takes care of enabling all required repositories.
The prefix FOREMAN_MAINTAIN_USE_BETA=1 has been added in BZ#1877397.
As the first issue is proven to not be an issue, and the second issue is fixed already, I am closing the bug. Feel free to re-open it if you have any concerns.
Thank you