Bug 2089580

This is fixed in bug #2044314

Created attachment 1886127 [details]
Hotfix RPM for Satellite 6.10.6

HOTFIX RPM is available for Satellite 6.10.3

INSTALL INSTRUCTIONS:

1. Take a complete backup or snapshot of Satellite 6.10.3 server

2. Download the hotfix RPM attached to this BZ and copy it to Satellite server

3. # yum install ./tfm-rubygem-katello-4.1.1.57-2.HOTFIXRHBZ2089580.el7sat.noarch.rpm --disableplugin=foreman-protector

4. # satellite-maintain service restart

CORRECTION: the above comment has inconsistent Satellite versions due to copy & paste error on my part. To clarify, this hotfix is applicable to Satellite 6.10.6 only.

Created attachment 1893266 [details]
Updated Hotfix RPM for Satellite 6.10.6

A new Hotfix RPM is available, which fixes both the Capsule Sync issue described here as well as the Errata Mail issue described in https://bugzilla.redhat.com/show_bug.cgi?id=2044314

INSTALL INSTRUCTIONS:

1. Take a complete backup or snapshot of Satellite 6.10.6 server

2. Download the hotfix RPM attached to this BZ and copy it to Satellite server

3. # yum install ./tfm-rubygem-katello-4.1.1.57-3.HOTFIXRHBZ2089580.el7sat.noarch.rpm --disableplugin=foreman-protector

4. # satellite-maintain service restart

An important note about this bug and hotfix: This bug affects only repositories in the Library environment + Default Organization View. Capsule syncs following CV publish/promote should not be affected by this issue. The intended behavior of 'Optimized' Capsule syncs, for the Library environment + Default Organization View, is that repositories are only synced on Capsules when some change is detected in the repo, as compared to the last time it was synced on Satellite. This Hotfix restores that intended behavior. Some repository syncs on Satellite may however find no changes since the last sync (even though the Capsules are still behind Satellite) and therefore still not trigger the automatic syncs on Capsules even with the Hotfix installed.

To ensure all repositories in the Library + Default Org View are up to date on all Capsules, regardless of whether the most recent syncs on Satellite detect any changes in the repository, use this approach:

1. Install the Hotfix using the steps in the above comment. ( https://bugzilla.redhat.com/show_bug.cgi?id=2089580#c12 ). This will ensure that when repository syncs on Satellite do detect changes, those changes are propagated out to any Capsules with the Library environment assigned.

2. Clear smart proxy sync histories for all root repositories on Satellite with this command:

  # echo "Katello::RootRepository.all.map(&:id).each { |repo_id| Katello::Repository.find(repo_id).clear_smart_proxy_sync_histories }" |foreman-rake console

3. Run 'Optimized' syncs of each Capsule.

*** Bug 2098271 has been marked as a duplicate of this bug. ***

Correction to the above script in comment #13 above. Step 2. (clear smart proxy sync histories) should use this command instead:

  # echo "Katello::Repository.where(content_view_version_id: 1).each(&:clear_smart_proxy_sync_histories)" |foreman-rake console

This will better target all repositories in the "Default Organization View"

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 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:5516

*** Bug 2098275 has been marked as a duplicate of this bug. ***