Unapplied migrations #13629
Replies: 7 comments 5 replies
-
|
What version did you upgrade from? |
Beta Was this translation helpful? Give feedback.
-
No.
Yes, when running the upgrade script. |
Beta Was this translation helpful? Give feedback.
-
|
I can reproduce the issue: Upgraded from 3.5.9 to 3.6.0, Python 3.11, no beta releases have been installed in between. |
Beta Was this translation helpful? Give feedback.
-
|
This is starting to get wierd: |
Beta Was this translation helpful? Give feedback.
-
|
I can reproduce it with a fresh install of NetBox. Seems to be a Django issue, though I can't find any related issue in their bug tracker. |
Beta Was this translation helpful? Give feedback.
-
|
This is probably related to some model attributes that we intentionally suppress when generating migrations. For example, we ignore I just checked and this continues to happen with Django 4.1 as well. It's likely tied to changes relating to translation support, but I can't recall noticing this warning before, so I'm not sure exactly what's changed. |
Beta Was this translation helpful? Give feedback.
-
|
I believe I've identified the cause of this: I believe it's because we're overriding certain model meta options in |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
I've recently updated to 3.6.0 and I noticed this red text:
However, when I run
manage.py showmigrations --list, everything shows as applied. And indeed, when I follow the instructions in the red text, it says "No changes detected" and "No migrations to apply." (I'm running this on a test machine, not the live server, no worries).Can I just ignore the message? Everything appears to be working anyway.
Beta Was this translation helpful? Give feedback.
All reactions