Actions
Issue #6861
closed
Migration from 3.2.0 to 3.3.z is broken
Start date:
Due date:
Estimated time:
Severity:
4. Urgent
Version:
Platform Release:
OS:
Triaged:
Yes
Groomed:
No
Sprint Candidate:
No
Tags:
Sprint:
Quarter:
Description
In trying to resolve the migration issues between 3.3.0 and 3.3.1, we accidentally introduced a new blocking issue between 3.2.0 and 3.3.z.
Both migration 0005 and 0009 need to be modified, again, such that they both specify that 'last_sync_revision_number' is nullable.
Actions
.
Make 'last_sync_revision_number' nullable in all migrations
[nocoverage]
closes: #6861 https://pulp.plan.io/issues/6861