[PULP-203] Fix a regression in migration 0056 #2041
Merged
Conversation
This file contains 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
|
@netsandbox any chance you can confirm that this fixes your migration? |
Having more than one collection version in the system prevents the migration 0056 to run, because null as a value is not allowed to appear more than once. We need to clean this up very careful, becuase on some systems the migration may have applied cleanly. fixes pulp#2040
mdellweg
force-pushed
the
2040_regression_migration_0056
branch
from
262e6e1 to
f47c012
Compare
|
@mdellweg I can confirm that this changes fixes the database migrations. |
Backport to 0.23: 💚 backport PR created✅ Backport PR branch: Backported as #2042 🤖 @patchback |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Having more than one collection version in the system prevents the migration 0056 to run, because null as a value is not allowed to appear more than once.
We need to clean this up very careful, becuase on some systems the migration may have applied cleanly.
fixes #2040