Bug 2215238

Summary: Optimized capsule sync doesn't sync recently published/promoted docker repositories
Product: Red Hat Satellite Reporter: Hao Chang Yu <hyu>
Component: Capsule - ContentAssignee: Samir Jha <sajha>
Status: VERIFIED --- QA Contact: Sam Bible <sbible>
Severity: high Docs Contact:
Priority: unspecified    
Version: 6.11.5CC: ben.formosa, ggainey, osousa, sajha, sbible, vcojot, zhunting
Target Milestone: 6.14.0Keywords: Triaged
Target Release: Unused   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: rubygem-katello-4.9.0.4-1 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
: 2227905 2231505 (view as bug list) 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 Hao Chang Yu 2023-06-15 06:42:22 UTC 
Description of problem:
If user triggers an optimized Capsule sync manually after publishing/promoting a content view containing docker repositories. The capsule sync task doesn't sync anything.

How reproducible:
Easy


Steps to Reproduce:
1. Set "Sync Capsules after content view promotion" to No
2. Create and sync a docker repository.
~~~
Registry URL: https://registry-1.docker.io/
Upstream Repository Name: library/hello-world

# Limit the tag to sync
Include Tags: latest
~~~

3. Create a content view and attach the docker repository to it. Publish and promote the content view.
4. Trigger a optimized capsule sync to sync the CV repositories for the first time to the Capsule.
5. In the docker repository page, include a new tag and sync it.

Include Tags: latest, linux

6. Publish and promote new version of the content view.
7. Trigger a optimized capsule sync again


Actual results:
The optimized capsule sync doesn't sync newly published docker repositories

Expected results:
Optimized capsule sync should sync the newly published docker repositories.


Additional info:
This is because the smart proxy sync history of the docker repositories didn't get clear after publishing/promoting the content view.
Comment 2 Samir Jha 2023-06-21 15:50:20 UTC 
Created redmine issue https://projects.theforeman.org/issues/36523 from this bug
Comment 5 Bryan Kearney 2023-06-30 20:03:08 UTC 
Moving this bug to POST for triage into Satellite since the upstream issue https://projects.theforeman.org/issues/36523 has been resolved.
Comment 7 Sam Bible 2023-08-03 19:09:01 UTC 
Verified on: 6.14 - Snap 10

Steps to Reproduce:
1. Set "Sync Capsules after content view promotion" to No
2. Create and sync a docker repository, using only one tag
3. Create a content view and attach the docker repository to it. Publish and promote the content view.
4. Trigger a optimized capsule sync to sync the CV repositories for the first time to the Capsule.
5. In the docker repository page, include a new tag and sync it.
6. Publish and promote new version of the content view.
7. Trigger a optimized capsule sync again


Actual results:
The optimized capsule sync resyncs after the new publish, to capture the new tags.

Expected results:
Optimized capsule sync should sync the newly published docker repositories.