-
Notifications
You must be signed in to change notification settings - Fork 54
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Migration 0056 is failing #2040
Comments
mdellweg
added a commit
to mdellweg/pulp_ansible
that referenced
this issue
Nov 22, 2024
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
added a commit
to mdellweg/pulp_ansible
that referenced
this issue
Nov 22, 2024
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
patchback bot
pushed a commit
that referenced
this issue
Nov 22, 2024
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 (cherry picked from commit 15561b9)
mdellweg
added a commit
that referenced
this issue
Nov 22, 2024
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 (cherry picked from commit 15561b9)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Originally posted by @netsandbox in #1052 (comment)
The text was updated successfully, but these errors were encountered: