Bug #36404
closedContainer image manifests synced without tags triggers "no content added"
Description
This thread has the details: https://community.theforeman.org/t/sync-status-for-docker-repos-shows-no-content-added-if-a-new-image-with-same-tag-was-synced/33483
In our code, we consider certain content unit types to be "primary_content". If a content type has no primary content, all content units for that type are primary content. If non-primary units are indexed, Katello will still report "no content added".
For some reason, for Docker, we have only tags as primary. We should look into adding manifests and consider why they weren't added in the first place.
Also, yum content types have RPMs and Errata as primary units. Perhaps module streams should be added?
This is not a regression. The issue has been around at least since Pulp 3 was introduced.
Updated by Chris Roberts over 1 year ago
- Target version changed from Katello 4.9.0 to Katello 4.10.0
- Triaged changed from No to Yes
Updated by Chris Roberts about 1 year ago
- Target version changed from Katello 4.10.0 to Katello 4.11.0
Updated by Ian Ballou 12 months ago
- Target version changed from Katello 4.11.0 to Katello 4.12.0
Updated by Quinn James 9 months ago
- Target version changed from Katello 4.12.0 to Katello 4.13.0
Bumping to 4.13
Updated by Ian Ballou 6 months ago
- Target version changed from Katello 4.13.0 to Katello 4.14.0
Updated by Chris Roberts 4 months ago
- Target version changed from Katello 4.14.0 to Katello 4.16.0
Updated by The Foreman Bot 3 months ago
- Status changed from New to Ready For Testing
- Assignee set to Ian Ballou
- Pull request https://github.com/Katello/katello/pull/11160 added
Updated by Anonymous 3 months ago
- Status changed from Ready For Testing to Closed
Applied in changeset katello|c3181b0e7ffb49505a56c11de5d248e3a028a19f.
Updated by Ian Ballou about 1 month ago
- Target version changed from Katello 4.16.0 to Katello 4.15.0