upgrade from 2.10-beta1 to anything newer fails

[zeroservices]

Hi,

we upgraded to 2.10-beta1 a couple of weeks ago as we had a lot of planning to do with import/exports within vrfs and overlapping address space..

Upgrading from 2.10-beta1 to anything newer (2.10-beta2, 2.10.0, ...) fails for me with:
Applying database migrations (python3 netbox/manage.py migrate)...
Traceback (most recent call last):
File "netbox/manage.py", line 10, in
execute_from_command_line(sys.argv)
File "/srv/netbox/releases/netbox-2.10.4/venv/lib64/python3.6/site-packages/django/core/management/init.py", line 401, in execute_from_command_line
utility.execute()
File "/srv/netbox/releases/netbox-2.10.4/venv/lib64/python3.6/site-packages/django/core/management/init.py", line 395, in execute
self.fetch_command(subcommand).run_from_argv(self.argv)
File "/srv/netbox/releases/netbox-2.10.4/venv/lib64/python3.6/site-packages/django/core/management/base.py", line 330, in run_from_argv
self.execute(*args, **cmd_options)
File "/srv/netbox/releases/netbox-2.10.4/venv/lib64/python3.6/site-packages/django/core/management/base.py", line 371, in execute
output = self.handle(*args, **options)
File "/srv/netbox/releases/netbox-2.10.4/venv/lib64/python3.6/site-packages/django/core/management/base.py", line 85, in wrapped
res = handle_func(*args, **kwargs)
File "/srv/netbox/releases/netbox-2.10.4/venv/lib64/python3.6/site-packages/django/core/management/commands/migrate.py", line 95, in handle
executor.loader.check_consistent_history(connection)
File "/srv/netbox/releases/netbox-2.10.4/venv/lib64/python3.6/site-packages/django/db/migrations/loader.py", line 306, in check_consistent_history
connection.alias,
django.db.migrations.exceptions.InconsistentMigrationHistory: Migration ipam.0041_routetarget is applied before its dependency extras.0052_customfield_cleanup on database 'default'.

Is there any way to fix this?

Thanks in advance!

[candlerb]

we upgraded to 2.10-beta1 a couple of weeks ago ...

Upgrading from 2.10-beta1 to anything newer (2.10-beta2, 2.10.0, ...) fails for me

Yes, that's expected. Upgrades from betas are never supported. It couldn't really have been flagged any more clearly, see the v2.10-beta1 release notes:

"WARNING: This is a beta release and is not suitable for production use. It is intended for development and evaluation purposes only. No upgrade path to the final v2.10 release will be provided from this beta, and users should assume that all data entered into the application will be lost."

The solution is to roll your database back to the last backup you took before going to the beta, and then upgrade from there.

[zeroservices]

we upgraded to 2.10-beta1 a couple of weeks ago ...
Upgrading from 2.10-beta1 to anything newer (2.10-beta2, 2.10.0, ...) fails for me

Yes, that's expected. Upgrades from betas are never supported. It couldn't really have been flagged any more clearly, see the v2.10-beta1 release notes:

You know how this works... you have a project, you need a missing feature. You just do it and forget about it... ;-)

Thanks. Will restore from backup.

[DanSheps]

Alternatively, you could take a backup of the current database and try and clean it up. I believe the changes are in the migrations and just need to be re-ordered. You can also clear out the migrations from beta and then --fake them