Bug 2225409

Summary:	Capsule autosync settings requires service restart to take effect
Product:	Red Hat Satellite	Reporter:	Vladimír Sedmík <vsedmik>
Component:	Tasks Plugin	Assignee:	Adam Ruzicka <aruzicka>
Status:	VERIFIED ---	QA Contact:	Vladimír Sedmík <vsedmik>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	6.14.0	CC:	aruzicka, pcreech, rlavi
Target Milestone:	6.14.0	Keywords:	Triaged
Target Release:	Unused
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:	rubygem-foreman-tasks-8.1.2	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:		Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Vladimír Sedmík 2023-07-25 09:27:29 UTC

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.

Comment 1 Vladimír Sedmík 2023-08-03 14:15:02 UTC

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.