Description of problem: On Satellite 6.12, importing an incremental export does not update the metadata properly on pulp. User can see the updated number of packages on the webUI, but clients consuming the repository still see the old count (from before importing the incremental). Forcing pulp to regenerate the metadata does create it properly and clients can then see the added packages. Version-Release number of selected component (if applicable): 6.12.2 How reproducible: I managed to reproduce it using RHEL 8 AppStream repository. Exporting a custom repository worked fine. I'm working to get a complete + incremental of a smaller Red Hat repository, so we can run tests faster. Steps to Reproduce: 1. Do complete export of a Red hat repository 2. Import complete on disconnected Satellite 3. Run "dnf repolist -v" on a client that consumes the repository 4. Export incremental of the same repository 5. Import incremental 6. On the client "dnf clean all && dnf repolist -v". Same number of packages as on step 3 are seen. Actual results: After incremental import, packages are not available for clients. Expected results: Added packages should be available for clients. Additional info:
Connecting redmine issue https://projects.theforeman.org/issues/36164 from this bug
Upstream bug assigned to paji
Moving this bug to POST for triage into Satellite since the upstream issue https://projects.theforeman.org/issues/36164 has been resolved.
Verified on 6.13 - Snap 14 Steps to Verify: Easiest to just link to Partha's excellent reproduction steps in this Katello PR https://github.com/Katello/katello/pull/10477 Expected results: After importing the incremental CV version and cleaning the repos on the Host, you see the proper number of repositories (in this case, 58 as opposed to 57) Actual results: After importing the incremental CV version and cleaning the repos on the Host, the proper number of repositories (in this case, 58 as opposed to 57) were present.
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.13 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-2023:2097
Created attachment 1964090 [details] Hotfix RPM for Satellite 6.12.4 A Hotfix RPM for Satellite 6.12.4 is now available. INSTALL INSTRUCTIONS: 1. Take a complete backup or snapshot of the Satellite 6.12.4 server 2. Download the hotfix RPM from this message's attachment. 3. # dnf install rubygem-katello-4.5.0.33-2.HOTFIXRHBZ2173756.el8sat.noarch.rpm --disableplugin=foreman-protector 4. # satellite-maintain service restart
Created attachment 1964092 [details] Hotfix RPM for Satellite 6.11.5 on RHEL8 A Hotfix RPM for Satellite 6.11.5 on RHEL8 is now available. INSTALL INSTRUCTIONS: 1. Take a complete backup or snapshot of the Satellite 6.11.5 server 2. Download the hotfix RPM from this message's attachment. 3. # dnf install ./rubygem-katello-4.3.0.52-2.HOTFIXRHBZ2173756.el8sat.noarch.rpm --disableplugin=foreman-protector 4. # satellite-maintain service restart
Created attachment 1964093 [details] Hotfix RPM for Satellite 6.11.5 on RHEL7 A Hotfix RPM for Satellite 6.11.5 on RHEL7 is now available. INSTALL INSTRUCTIONS: 1. Take a complete backup or snapshot of the Satellite 6.11.5 server 2. Download the hotfix RPM from this message's attachment. 3. # yum install ./tfm-rubygem-katello-4.3.0.52-2.HOTFIXRHBZ2173756.el7sat.noarch.rpm --disableplugin=foreman-protector 4. # satellite-maintain service restart