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.
Bug 2215238 - Optimized capsule sync doesn't sync recently published/promoted docker repositories
Summary: Optimized capsule sync doesn't sync recently published/promoted docker reposi...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Capsule - Content
Version: 6.11.5
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: 6.14.0
Assignee: Samir Jha
QA Contact: Sam Bible
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2023-06-15 06:42 UTC by Hao Chang Yu
Modified: 2024-02-19 19:43 UTC (History)
8 users (show)

Fixed In Version: rubygem-katello-4.9.0.4-1
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
: 2227905 2231505 (view as bug list)
Environment:
Last Closed: 2023-11-08 14:19:49 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Foreman Issue Tracker 36523 0 Normal Closed Optimized capsule sync doesn't sync recently published/promoted docker repositories 2024-02-16 18:34:36 UTC
Red Hat Issue Tracker SAT-18434 0 None None None 2023-06-15 14:11:35 UTC
Red Hat Product Errata RHSA-2023:6818 0 None None None 2023-11-08 14:19:59 UTC

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.
Comment 10 errata-xmlrpc 2023-11-08 14:19:49 UTC 
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
Note You need to log in before you can comment on or make changes to this bug.