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.
The repository setting for upgrades to 6.3 will try to set:
rhel-7-server-satellite-6.3-rpms
This repository will not exist until 6.3 GA and we will not be able to use foreman-maintain to upgrade 6.3 test systems to 6.3 Beta.
We either need to:
1) be able to skip this step entirely
2) for beta we need to have branding in place to use the beta repo IDs.
I'd prefer option 2 as it will be easier for our customers.
For 6.3 beta we will need the set the repo-ids to:
rhel-server-7-satellite-6-beta-rpms
so it will work out of the box during the beta period.
Once beta is complete we can go back to the standard 6.3 repos
Comment 7Satellite Program
2017-10-16 16:08:55 UTC
Upstream bug assigned to mmccune
Comment 8Satellite Program
2017-10-17 20:08:55 UTC
VERIFIED
# rpm -q rubygem-foreman_maintain
rubygem-foreman_maintain-0.1.1-1.el7sat.noarch
For 6.3, foreman-maintain sets beta repositories
D, [2017-12-19 06:19:49-0500 #10340] DEBUG -- : Running command subscription-manager repos --enable=rhel-7-server-rpms --enable=rhel-server-rhscl-7
-rpms --enable=rhel-server-7-satellite-6-beta-rpms with stdin nil
D, [2017-12-19 06:20:04-0500 #10340] DEBUG -- : output of the command:
Repository 'rhel-7-server-rpms' is enabled for this system.
Repository 'rhel-server-7-satellite-6-beta-rpms' is enabled for this system.
Repository 'rhel-server-rhscl-7-rpms' is enabled for this system.
and to skip repository setup
# foreman-maintain upgrade run --target-version 6.3 --whitelist='repositories-setup'
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, 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/RHBA-2018:0330