Upgrade Error: netbox ipam_iprange already exists

[unnuetz]

Hi,
i was running latest v2.11.12 version and decided now to upgrade to the latest v3.2.0.

What I did as recommended in the upgrade documentation is to create a postgres backup, then remove all old containers and remove postgres data volume.
Restored postgres data and start up all containers.

But now I got stuck:

What I did:

Stop all containers (old Version V2.11.12)
docker-compose down

Only start the DB
docker-compose up -d postgres

Take a DB backup
docker-compose exec -T netbox-docker_postgres_1 sh -c 'pg_dump -v -Fc -c -U netbox netbox' > "netbox_backup.pgdump"

Stop the database
docker-compose down

docker volume rm netbox-docker_netbox-postgres-data

git checkout release && git pull -p origin release
docker-compose pull

Restore the database

docker-compose up -d postgres
docker-compose exec -T postgres sh -c "pg_restore -v -Fc -c -U $POSTGRES_USER -d $POSTGRES_DB" < "netbox_backup.pgdump"

output:

...
pg_restore: creating FK CONSTRAINT "public.users_objectpermission_object_types users_objectpermissi_contenttype_id_594b1cc7_fk_django_co"
pg_restore: creating FK CONSTRAINT "public.users_objectpermission_groups users_objectpermissi_group_id_fb7ba6e0_fk_auth_grou"
pg_restore: creating FK CONSTRAINT "public.users_objectpermission_users users_objectpermission_users_user_id_16c0905d_fk_auth_user_id"
pg_restore: creating FK CONSTRAINT "public.users_token users_token_user_id_af964690_fk_auth_user_id"
pg_restore: creating FK CONSTRAINT "public.users_userconfig users_userconfig_user_id_afd44184_fk_auth_user_id"
pg_restore: creating FK CONSTRAINT "public.virtualization_cluster virtualization_cluster_group_id_de379828_fk"
pg_restore: creating FK CONSTRAINT "public.virtualization_cluster virtualization_cluster_site_id_4d5af282_fk"
pg_restore: creating FK CONSTRAINT "public.virtualization_cluster virtualization_cluster_tenant_id_bc2868d0_fk"
pg_restore: creating FK CONSTRAINT "public.virtualization_cluster virtualization_cluster_type_id_4efafb0a_fk"
pg_restore: creating FK CONSTRAINT "public.virtualization_virtualmachine virtualization_virtualmachine_cluster_id_6c9f9047_fk"
pg_restore: creating FK CONSTRAINT "public.virtualization_virtualmachine virtualization_virtualmachine_platform_id_a6c5ccb2_fk"
pg_restore: creating FK CONSTRAINT "public.virtualization_virtualmachine virtualization_virtualmachine_role_id_0cc898f9_fk"
pg_restore: creating FK CONSTRAINT "public.virtualization_virtualmachine virtualization_virtualmachine_tenant_id_d00d1d77_fk"
pg_restore: creating FK CONSTRAINT "public.virtualization_vminterface virtualization_vmint_parent_id_f86958e1_fk_virtualiz"
pg_restore: creating FK CONSTRAINT "public.virtualization_vminterface virtualization_vminterface_untagged_vlan_id_aea4fc69_fk"
pg_restore: creating FK CONSTRAINT "public.virtualization_vminterface virtualization_vminterface_virtual_machine_id_e9f89829_fk"
pg_restore: warning: errors ignored on restore: 989

Start all other containers
docker-compose up

netbox container will exit 1 after a short time with the following error message:

docker-compose logs netbox

Attaching to netbox-docker_netbox_1
netbox_1               | ⚙️ Applying database migrations
netbox_1               | 🧬 loaded config '/etc/netbox/config/configuration.py'
netbox_1               | 🧬 loaded config '/etc/netbox/config/extra.py'
netbox_1               | 🧬 loaded config '/etc/netbox/config/logging.py'
netbox_1               | 🧬 loaded config '/etc/netbox/config/plugins.py'
netbox_1               | Operations to perform:
netbox_1               |   Apply all migrations: admin, auth, circuits, contenttypes, dcim, django_rq, extras, ipam, sessions, social_django, taggit, tenancy, users, virtualization, wireless
netbox_1               | Running migrations:
netbox_1               | Traceback (most recent call last):
netbox_1               |   File "/opt/netbox/venv/lib/python3.9/site-packages/django/db/backends/utils.py", line 82, in _execute
netbox_1               |     return self.cursor.execute(sql)
netbox_1               | psycopg2.errors.DuplicateTable: relation "ipam_iprange" already exists
netbox_1               |
netbox_1               |
netbox_1               | The above exception was the direct cause of the following exception:
netbox_1               |
netbox_1               | Traceback (most recent call last):
netbox_1               |   File "/opt/netbox/netbox/./manage.py", line 10, in <module>
netbox_1               |     execute_from_command_line(sys.argv)
netbox_1               |   File "/opt/netbox/venv/lib/python3.9/site-packages/django/core/management/__init__.py", line 419, in execute_from_command_line
netbox_1               |     utility.execute()
netbox_1               |   File "/opt/netbox/venv/lib/python3.9/site-packages/django/core/management/__init__.py", line 413, in execute
netbox_1               |     self.fetch_command(subcommand).run_from_argv(self.argv)
netbox_1               |   File "/opt/netbox/venv/lib/python3.9/site-packages/django/core/management/base.py", line 354, in run_from_argv
netbox_1               |     self.execute(*args, **cmd_options)
netbox_1               |   File "/opt/netbox/venv/lib/python3.9/site-packages/django/core/management/base.py", line 398, in execute
netbox_1               |     output = self.handle(*args, **options)
netbox_1               |   File "/opt/netbox/venv/lib/python3.9/site-packages/django/core/management/base.py", line 89, in wrapped
netbox_1               |     res = handle_func(*args, **kwargs)
netbox_1               |   File "/opt/netbox/venv/lib/python3.9/site-packages/django/core/management/commands/migrate.py", line 244, in handle
netbox_1               |     post_migrate_state = executor.migrate(
netbox_1               |   File "/opt/netbox/venv/lib/python3.9/site-packages/django/db/migrations/executor.py", line 117, in migrate
netbox_1               |     state = self._migrate_all_forwards(state, plan, full_plan, fake=fake, fake_initial=fake_initial)
netbox_1               |   File "/opt/netbox/venv/lib/python3.9/site-packages/django/db/migrations/executor.py", line 147, in _migrate_all_forwards
netbox_1               |     state = self.apply_migration(state, migration, fake=fake, fake_initial=fake_initial)
netbox_1               |   File "/opt/netbox/venv/lib/python3.9/site-packages/django/db/migrations/executor.py", line 227, in apply_migration
netbox_1               |     state = migration.apply(state, schema_editor)
netbox_1               |   File "/opt/netbox/venv/lib/python3.9/site-packages/django/db/migrations/migration.py", line 126, in apply
netbox_1               |     operation.database_forwards(self.app_label, schema_editor, old_state, project_state)
netbox_1               |   File "/opt/netbox/venv/lib/python3.9/site-packages/django/db/migrations/operations/models.py", line 92, in database_forwards
netbox_1               |     schema_editor.create_model(model)
netbox_1               |   File "/opt/netbox/venv/lib/python3.9/site-packages/django/db/backends/base/schema.py", line 345, in create_model
netbox_1               |     self.execute(sql, params or None)
netbox_1               |   File "/opt/netbox/venv/lib/python3.9/site-packages/django/db/backends/base/schema.py", line 145, in execute
netbox_1               |     cursor.execute(sql, params)
netbox_1               |   File "/opt/netbox/venv/lib/python3.9/site-packages/django/db/backends/utils.py", line 66, in execute
netbox_1               |     return self._execute_with_wrappers(sql, params, many=False, executor=self._execute)
netbox_1               |   File "/opt/netbox/venv/lib/python3.9/site-packages/django/db/backends/utils.py", line 75, in _execute_with_wrappers
netbox_1               |     return executor(sql, params, many, context)
netbox_1               |   File "/opt/netbox/venv/lib/python3.9/site-packages/django/db/backends/utils.py", line 84, in _execute
netbox_1               |     return self.cursor.execute(sql, params)
netbox_1               |   File "/opt/netbox/venv/lib/python3.9/site-packages/django/db/utils.py", line 90, in __exit__
netbox_1               |     raise dj_exc_value.with_traceback(traceback) from exc_value
netbox_1               |   File "/opt/netbox/venv/lib/python3.9/site-packages/django/db/backends/utils.py", line 82, in _execute
netbox_1               |     return self.cursor.execute(sql)
netbox_1               | django.db.utils.ProgrammingError: relation "ipam_iprange" already exists
netbox_1               |
netbox_1               |   Applying ipam.0050_iprange...

I was wondering if it could have something to do with the restore command i am using:

In the Wiki the command is beeing used:
gunzip -c db_dump.sql.gz | docker-compose exec -T postgres sh -c '**psql -U $POSTGRES_USER $POSTGRES_DB**'
and i am using:
docker-compose exec -T postgres sh -c "**pg_restore** -v -Fc -c -U $POSTGRES_USER -d $POSTGRES_DB" < "netbox_backup.pgdump"

if i am trying to use pgsql -U with the dump file without compression gz used. i am receiving the following error:

docker-compose exec -T postgres sh -c "psql -U $POSTGRES_USER -d $POSTGRES_DB" < "netbox_backup.pgdump"
The input is a PostgreSQL custom-format dump.
Use the pg_restore command-line client to restore this dump to a database.