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:
While testing BZ#2173535 it seems there is still some issue pending which requires service restart for the settings change to take effect.


Version-Release number of selected component (if applicable):
6.14.0 snap 8


How reproducible:
always


Steps to Reproduce:
1. follow https://bugzilla.redhat.com/show_bug.cgi?id=2173535


Actual results:
1. After flipping the autosync to 'No', the first CV promotion is still synced, but consequent publish/promotes are not (which is expected).
2. After flipping the autosync back to 'Yes', the capsule isn't autosynced until the services are restarted. This behavior resembles https://bugzilla.redhat.com/show_bug.cgi?id=2157869 but needs different fix.


Expected results:
Proper behavior without need to restart services.

Verified in 6.14.0 snap 10.

Capsule is now synced properly according to settings (foreman_proxy_content_auto_sync) without need for service restart.

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