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.
Description of problem:
https://access.redhat.com/documentation/en-us/red_hat_satellite/6.12/html-single/upgrading_and_updating_red_hat_satellite/index#updating_disconnected_satellite_server
For disconnected Satellite update we say to reposync packages locally on Satellite connected to internet using this command:
# reposync --delete --download-metadata -p ~/Satellite-repos -n \
--repoid rhel-8-for-x86_64-baseos-rpms \
--repoid rhel-8-for-x86_64-appstream-rpms \
--repoid satellite-6.12-for-rhel-8-x86_64-rpms \
--repoid satellite-maintenance-6.12-for-rhel-8-x86_64-rpms
However foreman-protector locking plugin prevents to download majority of required packages, making disconnected Satellite update illusory.
Version-Release number of selected component (if applicable):
6.12.4
How reproducible:
deterministic
Steps to Reproduce:
1. Run documented reposync command
# reposync --delete --download-metadata -p ~/Satellite-repos -n \
--repoid rhel-8-for-x86_64-baseos-rpms \
--repoid rhel-8-for-x86_64-appstream-rpms \
--repoid satellite-6.12-for-rhel-8-x86_64-rpms \
--repoid satellite-maintenance-6.12-for-rhel-8-x86_64-rpms
2. Check the size of a synced content
# du -sh ~/Satellite-repos
1.5G Satellite-repos
Actual results:
limited content is being synced
1.5G Satellite-repos
Expected results:
all content is being synced
14G Satellite-repos
Additional info:
Workaround is to run reposync command with this additional option
# reposync --disableplugin=foreman-protector ...
VERIFIED.
@Satellite 6.14.0 Snap8
rubygem-foreman_maintain-1.3.2-1.el8sat.noarch
by the reproducer described in comment#0:
1) On Satellite 6.14 run documented reposync command (used 6.13 repos as 6.14 repos are not available yet)
# reposync --delete --download-metadata -p ~/Satellite-repos -n \
--repoid rhel-8-for-x86_64-baseos-rpms \
--repoid rhel-8-for-x86_64-appstream-rpms \
--repoid satellite-6.13-for-rhel-8-x86_64-rpms \
--repoid satellite-maintenance-6.13-for-rhel-8-x86_64-rpms
2) Check the size of a synced content
# du -sh ~/Satellite-repos
14G Satellite-repos
>>> dnf reposync sub-command is not locked down by foreman-protector plugin
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 (Important: Satellite 6.14 security and 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/RHSA-2023:6818