Bug 1991495

Summary: Capsule is not synced automatically after repo sync/publish
Product: Red Hat Satellite Reporter: Vladimír Sedmík <vsedmik>
Component: Capsule - ContentAssignee: satellite6-bugs <satellite6-bugs>
Status: CLOSED DUPLICATE QA Contact: Vladimír Sedmík <vsedmik>
Severity: high Docs Contact:
Priority: high    
Version: 6.10.0CC: ahumbe, jsherril
Target Milestone: 6.10.0Keywords: Regression, Triaged
Target Release: Unused   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2021-08-09 16:51:58 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 Vladimír Sedmík 2021-08-09 09:42:36 UTC 
Description of problem:
The capsule is not synced automatically after new repo is created and synced despite the Administer > Settings > Content > Sync Capsules after Content View promotion is set to Yes.


Version-Release number of selected component (if applicable):
6.10.0 snap 10


How reproducible:
always


Steps to Reproduce:
1. Have a Satellite and a Capsule in the Library LCE
2. Create a new product and repo and sync it.


Actual results:
The repo is not synced to the capsule. I can see the "Sync Repository on Capsule(s)" task with 0 duration, but it is not followed by any "Synchronize capsule '<CAPS-FQDN>'" task and the content is not synchronized.


Expected results:
Content being automatically synchronized to the capsule.


Additional info:
Seems to be a regression since 6.9, where this works as expected.
Comment 2 Justin Sherrill 2021-08-09 16:51:58 UTC 

*** This bug has been marked as a duplicate of bug 1982344 ***