Closed peteeckel closed 1 year ago
Yes, this is expected. You'll need to upgrade from a v3.4 database (or from an empty database) for each beta, as the migrations have been modified. This has always been the case for our beta releases.
Thanks, I thought that would be the case but just wanted to be sure.
NetBox version
3.5-beta2
Python version
3.8
Steps to Reproduce
Upgrade from 3.5-beta1 to 3.5-beta2
Expected Behavior
A working NetBox 3.5-beta2 installation
Observed Behavior
After the upgrade from 3.5-beta1 to 3.5-beta2, the NetBox instance is pretty much unusable. Almost every click into the user ID (both Dashboard widgets and Sidebar items) results in an Exception (see below).
This is obviously caused by a change in the migration `extras/migrations/0085_synced_data.py', which has additional columns in 3.5-beta2 as compared to 3.5-beta1:
Not sure if this qualifies as a real bug, as it is an incompatibility between two beta versions (should this be supported?), but you may run into it while testing. The workaround is to drop and re-create the NetBox database or to create the columns manually.