Avoid Status.DoesNotExist during loaddata; document PostgreSQL to MySQL data migration #954
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.
Fixes: #555
During
nautobot-server loaddata
, the attempt inCable.__init__
to cache any pre-existingStatus
for the cable was throwing an exception because the Status models hadn't been written to the database yet. SinceCable._orig_status
is only used in theupdate_connected_endpoints
signal handler forpost_save
, and only in the case wherecreated == False
, we can safely skip setting_orig_status
in the case where the Cable is being newly created and doesn't pre-exist in the database.That's my working theory anyway - this change definitely allows
invoke loaddata
to run without errors now, but our unit test coverage for this signal path appears pretty close to zero, so please hold me accountable here. :-)