Skip to content
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

Migrations not reversible #316

Closed
whitej6 opened this issue Mar 13, 2024 · 4 comments
Closed

Migrations not reversible #316

whitej6 opened this issue Mar 13, 2024 · 4 comments
Labels
type: bug Something isn't working as expected

Comments

@whitej6
Copy link
Contributor

whitej6 commented Mar 13, 2024

Environment

  • Python version: 3.11
  • Nautobot version: 2.1.x
  • nautobot-device-lifecycle-mgmt version: latest

Expected Behavior

nautobot-server migrate nautobot_device_lifecycle_mgmt zero

Observed Behavior

Following migrations do not have a reverse_code

  • 0019
  • 0017
  • 0008

Following tables need to be empty to be able to be reversible

  • 0004_squash__0004_0014_0015_0016 - nautobot_device_lifecycle_mgmt_validatedsoftwarelcm

Steps to Reproduce

@whitej6
Copy link
Contributor Author

whitej6 commented Mar 13, 2024

0004_squash__0004_0014_0015_0016 - causes problems on migrate zero, after migrate zero this entry many need to be manually removed from the django_migrations table.

@ghost
Copy link

ghost commented Jun 21, 2024

Also affected by this, I believe - 0019_cve_and_contract_m2m_migration is not reversible when nautobot-server migrate nautobot_device_lifecycle_mgmt zero

@bryanculver
Copy link
Member

We're going to constrain the scope of this story to addressing the missing reverse_code. The squash migration will be a separate fix.

@bryanculver bryanculver added the type: bug Something isn't working as expected label Sep 27, 2024
@gsnider2195
Copy link
Contributor

Fixed by #381

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type: bug Something isn't working as expected
Projects
None yet
Development

No branches or pull requests

3 participants