Project

Profile

Help

Issue #6861

Migration from 3.2.0 to 3.3.z is broken

Added by dalley about 1 year ago. Updated about 1 year ago.

Status:
CLOSED - CURRENTRELEASE
Priority:
Normal
Assignee:
Sprint/Milestone:
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.

Associated revisions

Revision 8f21aee1 View on GitHub
Added by dalley about 1 year ago

Make 'last_sync_revision_number' nullable in all migrations

[nocoverage]

closes: #6861 https://pulp.plan.io/issues/6861

History

#1 Updated by pulpbot about 1 year ago

  • Status changed from ASSIGNED to POST

#2 Updated by dalley about 1 year ago

  • Status changed from POST to MODIFIED

#3 Updated by ttereshc about 1 year ago

  • Sprint/Milestone set to Pulp RPM 3.4.0

#4 Updated by ttereshc about 1 year ago

  • Status changed from MODIFIED to CLOSED - CURRENTRELEASE

Please register to edit this issue

Also available in: Atom PDF