pulp image upgrade from 3.80 to 3.113(stable version)#4782
Merged
Conversation
Signed-off-by: pullan1 <sudha.pullalaravu@dell.com>
abhishek-sa1
approved these changes
Jun 22, 2026
snarthan
approved these changes
Jun 22, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary: Pulp 3.80 → 3.113 Upgrade
Root Cause
Pulp 3.80: Bug caused cosign signatures (.sig files) to be silently skipped during sync
Pulp 3.113: Bug fixed - now correctly attempts to sync cosign signatures
Registry.k8s.io (June 2026): Infrastructure change - signatures only exist in one canonical region (us-central1-docker.pkg.dev)
Result: 404 errors when Pulp 3.113 tries to fetch non-existent .sig files
Fix Applied
Added --exclude-tags '["sha256.sig"]' parameter to all 10 Pulp container remote commands in config.py:164-182:
Prevents Pulp from attempting to sync signature files
Works around registry.k8s.io infrastructure limitation
Allows container image syncs to succeed
Replicates the "silent skip" behavior from Pulp 3.80
Bottom Line
The upgrade exposed a pre-existing registry infrastructure issue. The fix explicitly excludes problematic signature files while maintaining successful image synchronization.