Migration to 1.4.0 may fail if default statuses have been modified. #2215
Labels
impact: high
High severity bugs causing system wide impact
type: bug
Something isn't working as expected
Milestone
Environment
Upgrading Nautobot from 1.3.6 to 1.4.0 using the instructions provided in the documentation introduced a conflict with the status
'Retired' if the existing environment already have this status implemented.
The error occurs during migration when running:
Applying dcim.0014_location_status_data_migration...Unexpected error while running data migration to populate status for dcim.location: duplicate key value violates unique constraint "extras_status_name_key"
DETAIL: Key (name)=(Retired) already exists.
Temporarily solved by renaming the 'Retired' status.
Steps to Reproduce
Expected Behavior
Successful data migration
Observed Behavior
Unexpected error during post upgrade due to duplicate keys, status name 'Retired'.
The text was updated successfully, but these errors were encountered: