Bug 2202990

Summary:	Capsule synchronization is not initiated automatically when "Sync Capsules after content view promotion" setting is set to "True"
Product:	Red Hat Satellite	Reporter:	Jayant Bhatia <jbhatia>
Component:	Capsule - Content	Assignee:	Samir Jha <sajha>
Status:	CLOSED DUPLICATE	QA Contact:	Satellite QE Team <sat-qe-bz-list>
Severity:	high	Docs Contact:
Priority:	high
Version:	6.13.0	CC:	ahumbe, iballou, sajha
Target Milestone:	6.14.0	Keywords:	PrioBumpGSS, Regression
Target Release:	Unused
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2023-06-27 16:06:57 UTC	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 Jayant Bhatia 2023-05-11 02:02:46 UTC

Description of problem:

The Capsule synchronization is not initiated automatically after publishing/promoting new version of content view even when "Sync Capsules after content view promotion" is set to "Yes"


Version-Release number of selected component (if applicable): Satellite-6.13.0


How reproducible: Always


Steps to Reproduce:

1. Ensure setting "Sync Capsules after content view promotion" is set to "Yes"
2. Add Library lifecycle environment to Capsule. Enable and Sync any random repository on Satellite server.
3. Create a new lifecycle environment (say 'lc_new') and add 'lc_new' environment to the Capsule.
4. Create a new content view (say 'cv_new') and publish a new version of 'cv_new' to 'Library' lifecycle environment. Promote the newly published version of  'cv_new' to 'lc_new' lifecycle environment.


Actual results: Capsule synchronization is not automatically initiated even when a new repository is synchronized on Satellite. Also Capsule sync is not initiated automatically after publish/promote of 'cv_new' content view.


Expected results: Since Library environment is added to the Capsule, synchronizing new repository on Satellite should initiate Capsule sync. Also publish/promote of cv_new to lc_new environment should also initiate a Capsule sync task.

Comment 3 Ian Ballou 2023-05-18 16:22:33 UTC

Let's investigate https://bugzilla.redhat.com/show_bug.cgi?id=2173535 at the same time as looking into this issue.