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.
DescriptionBrad Buckingham
2022-06-03 15:52:48 UTC
+++ This bug was initially created as a clone of Bug #2087753 +++
The self-upgrade mechanism deals with system repositories. This slows downs the overall self-upgrade command as it involves 'yum-config-manager' and 'subscription-manager' to enable and disable repositories. Instead of this the yum options are better choice which does not need to enable/disable system repositories and get the job done of updating packages.
--- Additional comment from on 2022-05-18T12:49:54Z
Created from redmine issue https://projects.theforeman.org/issues/34937
--- Additional comment from on 2022-05-18T12:49:56Z
Upstream bug assigned to aupadhye
--- Additional comment from on 2022-05-19T16:04:56Z
Moving this bug to POST for triage into Satellite since the upstream issue https://projects.theforeman.org/issues/34937 has been resolved.
Verified.
Tested on Satellite 6.10.7 Snap 1.0
Version: rubygem-foreman_maintain-0.8.31-1.el7sat.noarch
1. # foreman-maintain self-upgrade
2. Add repo for next major version maintenance repo under /etc/yum.repos.d/ for disconnected/testing environment.
3. # foreman-maintain self-upgrade --maintenance-repo-label sat-maintain
OR
3. # MAINTENANCE_REPO_LABEL='sat-maintain' foreman-maintain self-upgrade
Observation:
By not dealing with system repos, like saving enabled repos into yaml, and enabling/disabling system repos, the new self-upgrade mechanism makes it easier to update satellite-maintain/rubygem-foreman_maintain packages with yum options.
When using rhsm repos in connected environment it uses yum options "--enablerepo=rhel-7-server-rpms --enablerepo=rhel-server-rhscl-7-rpms --enablerepo=rhel-7-server-satellite-maintenance-6.11-rpms" and for disconnected/testing environment it just uses yum options "--enablerepo=sat-maintain", along with "--disableplugin=foreman-protector".
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 (Satellite Maintenance 6.10.7 Async Bug Fix Update), 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-2022:5519