[main] add initContainer for handle-image-data command - #267
Closed
jerabekjiri wants to merge 1 commit into
Closed
jerabekjiri wants to merge 1 commit into
jerabekjiri wants to merge 1 commit into
Conversation
Contributor
Author
|
I just noticed there's another solution #266. My approach uses init containers. We can decide with which solution we want to go with. |
Contributor
Author
|
/retest |
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
1 participant
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
When upgrading from 2.6 to 2.7, the pulp_container migration adds a data field to the Manifest model but leaves it NULL for existing manifests. The operator never runs
pulpcore-manager container-handle-image-datato populate it from the existing artifacts, which can result in broken execution environments after upgrade.Fix
Add a handle-image-data init container that runs
pulpcore-manager container-handle-image-dataautomatically after DB migrations. The command populates manifest.data from existing artifacts for all manifests (both synced and pushed) as part of the upgrade process, so customers don't have to run it manually.The command is a no-op when all manifests already have data populated.
ADDITIONAL INFORMATION