Upgrade from 4.3.7 to 4.4.3: django.db.utils.ProgrammingError: constraint "dcim_platform_name" of relation "dcim_platform" does not exist

[donix42]

We just attempted to upgrade our netbox-docker based 4.3.7 to 4.4.3 and during fist container start the netbox-1 container is reported "unhealthy" and while examining the logs there is a Django backtrace concerning a missing constraint. However, the netbox instance is up and seems OK and a subsequent restarts do not show any issues. Is this a cosmetical issue due to an unhandled exception or should we be worried and roll back?

The exception in question is:

django.db.utils.ProgrammingError: constraint "dcim_platform_name" of relation "dcim_platform" does not exist

We are running a customised (as in with plugin build enabled) netbox-docker, although with a bare metal postgres-14 instead of a containerised one.

This is the output from "docker compose logs" during first boot of 4.4.3:

netbox1:~/netbox-docker# docker compose up -d
[+] Running 7/7
 ✔ Network netbox-docker_default                  Created                                                                                                                                   0.0s
 ✔ Container netbox-docker-netbox-housekeeping-1  Started                                                                                                                                   0.5s
 ✔ Container netbox-docker-redis-1                Started                                                                                                                                   0.5s
 ✔ Container netbox-docker-redis-cache-1          Started                                                                                                                                   0.5s
 ✘ Container netbox-docker-netbox-1               Error                                                                                                                                    24.3s
 ✔ Container netbox-docker-netbox-worker-1        Created                                                                                                                                   0.1s
 ✔ Container netbox-docker-tls-1                  Started                                                                                                                                   0.8s
dependency failed to start: container netbox-docker-netbox-1 is unhealthy
root@lkp2netbox1:~/netbox-docker# docker compose logs
netbox-housekeeping-1  | ⚙️ Applying database migrations
netbox-housekeeping-1  | 🧬 loaded config '/etc/netbox/config/configuration.py'
netbox-housekeeping-1  | 🧬 loaded config '/etc/netbox/config/extra.py'
netbox-housekeeping-1  | 🧬 loaded config '/etc/netbox/config/logging.py'
netbox-housekeeping-1  | 🧬 loaded config '/etc/netbox/config/plugins.py'
netbox-housekeeping-1  | Operations to perform:
netbox-housekeeping-1  |   Apply all migrations: account, auth, circuits, contenttypes, core, dcim, django_rq, extras, ipam, netbox_topology_views, sessions, social_django, taggit, tenancy, thumbnail, users, virtualization, vpn, wireless
netbox-housekeeping-1  | Running migrations:
netbox-housekeeping-1  |   Applying core.0016_job_log_entries... OK
netbox-housekeeping-1  |   Applying core.0017_objectchange_message... OK
netbox-housekeeping-1  |   Applying core.0018_concrete_objecttype... OK
netbox-housekeeping-1  |   Applying core.0019_configrevision_active... OK
netbox-housekeeping-1  |   Applying dcim.0211_platform_manufacturer_uniqueness... OK
netbox-housekeeping-1  |   Applying dcim.0212_interface_tx_power_negative... OK
netbox-housekeeping-1  |   Applying dcim.0213_platform_parent... OK
netbox-housekeeping-1  |   Applying dcim.0214_platform_rebuild... OK
netbox-housekeeping-1  |   Applying dcim.0215_rackreservation_status... OK
netbox-housekeeping-1  |   Applying extras.0130_imageattachment_description... OK
netbox-housekeeping-1  |   Applying extras.0131_concrete_objecttype... OK
netbox-housekeeping-1  |   Applying extras.0132_configcontextprofile... OK
netbox-housekeeping-1  |   Applying extras.0133_make_cf_minmax_decimal... OK
netbox-housekeeping-1  |   Applying thumbnail.0001_initial... OK
netbox-housekeeping-1  |   Applying users.0011_concrete_objecttype... OK
netbox-housekeeping-1  |   Applying users.0012_drop_django_admin_log_table... OK
netbox-housekeeping-1  | ⚙️ Running trace_paths
netbox-housekeeping-1  | 🧬 loaded config '/etc/netbox/config/configuration.py'
netbox-housekeeping-1  | 🧬 loaded config '/etc/netbox/config/extra.py'
netbox-housekeeping-1  | 🧬 loaded config '/etc/netbox/config/logging.py'
netbox-housekeeping-1  | 🧬 loaded config '/etc/netbox/config/plugins.py'
netbox-housekeeping-1  | Found no missing console port paths; skipping
netbox-housekeeping-1  | Found no missing console server port paths; skipping
netbox-housekeeping-1  | Found no missing interface paths; skipping
netbox-housekeeping-1  | Found no missing power feed paths; skipping
netbox-housekeeping-1  | Found no missing power outlet paths; skipping
netbox-housekeeping-1  | Found no missing power port paths; skipping
netbox-housekeeping-1  | Finished.
netbox-housekeeping-1  | ⚙️ Removing stale content types
netbox-housekeeping-1  | 🧬 loaded config '/etc/netbox/config/configuration.py'
netbox-housekeeping-1  | 🧬 loaded config '/etc/netbox/config/extra.py'
netbox-housekeeping-1  | 🧬 loaded config '/etc/netbox/config/logging.py'
netbox-housekeeping-1  | 🧬 loaded config '/etc/netbox/config/plugins.py'
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: account, auth, circuits, contenttypes, core, dcim, django_rq, extras, ipam, netbox_topology_views, sessions, social_django, taggit, tenancy, thumbnail, users, virtualization, vpn, wireless
netbox-1               | Running migrations:
netbox-1               | Traceback (most recent call last):
netbox-1               |   File "/opt/netbox/venv/lib/python3.12/site-packages/django/db/backends/utils.py", line 103, in _execute
netbox-1               |     return self.cursor.execute(sql)
netbox-1               |            ^^^^^^^^^^^^^^^^^^^^^^^^
netbox-1               |   File "/opt/netbox/venv/lib/python3.12/site-packages/psycopg/cursor.py", line 97, in execute
netbox-1               |     raise ex.with_traceback(None)
netbox-1               | psycopg.errors.UndefinedObject: constraint "dcim_platform_name" of relation "dcim_platform" does not exist
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.12/site-packages/django/core/management/__init__.py", line 442, in execute_from_command_line
netbox-1               |     utility.execute()
netbox-1               |   File "/opt/netbox/venv/lib/python3.12/site-packages/django/core/management/__init__.py", line 436, in execute
netbox-1               |     self.fetch_command(subcommand).run_from_argv(self.argv)
netbox-1               |   File "/opt/netbox/venv/lib/python3.12/site-packages/django/core/management/base.py", line 416, in run_from_argv
netbox-1               |     self.execute(*args, **cmd_options)
netbox-1               |   File "/opt/netbox/venv/lib/python3.12/site-packages/django/core/management/base.py", line 460, in execute
netbox-1               |     output = self.handle(*args, **options)
netbox-1               |              ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
netbox-1               |   File "/opt/netbox/venv/lib/python3.12/site-packages/django/core/management/base.py", line 107, in wrapper
netbox-1               |     res = handle_func(*args, **kwargs)
netbox-1               |           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^
netbox-1               |   File "/opt/netbox/venv/lib/python3.12/site-packages/django/core/management/commands/migrate.py", line 353, in handle
netbox-1               |     post_migrate_state = executor.migrate(
netbox-1               |                          ^^^^^^^^^^^^^^^^^
netbox-1               |   File "/opt/netbox/venv/lib/python3.12/site-packages/django/db/migrations/executor.py", line 135, in migrate
netbox-1               |     state = self._migrate_all_forwards(
netbox-1               |             ^^^^^^^^^^^^^^^^^^^^^^^^^^^
netbox-1               |   File "/opt/netbox/venv/lib/python3.12/site-packages/django/db/migrations/executor.py", line 167, in _migrate_all_forwards
netbox-1               |     state = self.apply_migration(
netbox-1               |             ^^^^^^^^^^^^^^^^^^^^^
netbox-1               |   File "/opt/netbox/venv/lib/python3.12/site-packages/django/db/migrations/executor.py", line 255, in apply_migration
netbox-1               |     state = migration.apply(state, schema_editor)
netbox-1               |             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
netbox-1               |   File "/opt/netbox/venv/lib/python3.12/site-packages/django/db/migrations/migration.py", line 132, in apply
netbox-1               |     operation.database_forwards(
netbox-1               |   File "/opt/netbox/venv/lib/python3.12/site-packages/django/db/migrations/operations/fields.py", line 241, in database_forwards
netbox-1               |     schema_editor.alter_field(from_model, from_field, to_field)
netbox-1               |   File "/opt/netbox/venv/lib/python3.12/site-packages/django/db/backends/base/schema.py", line 912, in alter_field
netbox-1               |     self._alter_field(
netbox-1               |   File "/opt/netbox/venv/lib/python3.12/site-packages/django/db/backends/postgresql/schema.py", line 274, in _alter_field
netbox-1               |     super()._alter_field(
netbox-1               |   File "/opt/netbox/venv/lib/python3.12/site-packages/django/db/backends/base/schema.py", line 998, in _alter_field
netbox-1               |     self.execute(self._delete_unique_sql(model, constraint_name))
netbox-1               |   File "/opt/netbox/venv/lib/python3.12/site-packages/django/db/backends/postgresql/schema.py", line 48, in execute
netbox-1               |     return super().execute(sql, None)
netbox-1               |            ^^^^^^^^^^^^^^^^^^^^^^^^^^
netbox-1               |   File "/opt/netbox/venv/lib/python3.12/site-packages/django/db/backends/base/schema.py", line 204, in execute
netbox-1               |     cursor.execute(sql, params)
netbox-1               |   File "/opt/netbox/venv/lib/python3.12/site-packages/django/db/backends/utils.py", line 79, in execute
netbox-1               |     return self._execute_with_wrappers(
netbox-1               |            ^^^^^^^^^^^^^^^^^^^^^^^^^^^^
netbox-1               |   File "/opt/netbox/venv/lib/python3.12/site-packages/django/db/backends/utils.py", line 92, in _execute_with_wrappers
netbox-1               |     return executor(sql, params, many, context)
netbox-1               |            ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
netbox-1               |   File "/opt/netbox/venv/lib/python3.12/site-packages/django/db/backends/utils.py", line 100, in _execute
netbox-1               |     with self.db.wrap_database_errors:
netbox-1               |   File "/opt/netbox/venv/lib/python3.12/site-packages/django/db/utils.py", line 91, in __exit__
netbox-1               |     raise dj_exc_value.with_traceback(traceback) from exc_value
netbox-1               |   File "/opt/netbox/venv/lib/python3.12/site-packages/django/db/backends/utils.py", line 103, in _execute
netbox-1               |     return self.cursor.execute(sql)
netbox-1               |            ^^^^^^^^^^^^^^^^^^^^^^^^
netbox-1               |   File "/opt/netbox/venv/lib/python3.12/site-packages/psycopg/cursor.py", line 97, in execute
netbox-1               |     raise ex.with_traceback(None)
netbox-1               | django.db.utils.ProgrammingError: constraint "dcim_platform_name" of relation "dcim_platform" does not exist
netbox-1               |   Applying dcim.0211_platform_manufacturer_uniqueness...🧬 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               | 153 objects imported automatically (use -v 2 for details).
netbox-1               |
netbox-1               | 💡 Superuser Username: admin, E-Mail: xxx

Having a look at the suspect relation in Postgres shows:

postgres@netbox1:~$ psql
psql (14.19 (Ubuntu 14.19-1.pgdg22.04+1))
Type "help" for help.

postgres=# \c netbox;
netbox=# \d dcim_platform;
                                           Table "public.dcim_platform"
       Column       |           Type           | Collation | Nullable |                  Default
--------------------+--------------------------+-----------+----------+-------------------------------------------
 id                 | bigint                   |           | not null | nextval('dcim_platform_id_seq'::regclass)
 name               | character varying(100)   |           | not null |
 slug               | character varying(100)   |           | not null |
 manufacturer_id    | bigint                   |           |          |
 created            | timestamp with time zone |           |          |
 last_updated       | timestamp with time zone |           |          |
 description        | character varying(200)   |           | not null |
 custom_field_data  | jsonb                    |           | not null |
 config_template_id | bigint                   |           |          |
 parent_id          | bigint                   |           |          |
 level              | integer                  |           | not null |
 lft                | integer                  |           | not null |
 rght               | integer                  |           | not null |
 tree_id            | integer                  |           | not null |
 comments           | text                     |           | not null |
Indexes:
    "dcim_platform_pkey" PRIMARY KEY, btree (id)
    "dcim_platform_config_template_id_013a4d3c" btree (config_template_id)
    "dcim_platform_manufacturer_id_83f72d3d" btree (manufacturer_id)
    "dcim_platform_manufacturer_name" UNIQUE CONSTRAINT, btree (manufacturer_id, name)
    "dcim_platform_manufacturer_slug" UNIQUE CONSTRAINT, btree (manufacturer_id, slug)
    "dcim_platform_name" UNIQUE, btree (name) WHERE manufacturer_id IS NULL
    "dcim_platform_parent_id_795c7101" btree (parent_id)
    "dcim_platform_slug" UNIQUE, btree (slug) WHERE manufacturer_id IS NULL
    "dcim_platform_slug_b0908ae4" btree (slug)
    "dcim_platform_slug_b0908ae4_like" btree (slug varchar_pattern_ops)
    "dcim_platform_tree_id_ca32aeb8" btree (tree_id)
Check constraints:
    "dcim_platform_level_check" CHECK (level >= 0)
    "dcim_platform_lft_check" CHECK (lft >= 0)
    "dcim_platform_rght_check" CHECK (rght >= 0)
    "dcim_platform_tree_id_check" CHECK (tree_id >= 0)
Foreign-key constraints:
    "dcim_platform_config_template_id_013a4d3c_fk_extras_co" FOREIGN KEY (config_template_id) REFERENCES extras_configtemplate(id) DEFERRABLE INITIALLY DEFERRED
    "dcim_platform_manufacturer_id_83f72d3d_fk" FOREIGN KEY (manufacturer_id) REFERENCES dcim_manufacturer(id) DEFERRABLE INITIALLY DEFERRED
    "dcim_platform_parent_id_795c7101_fk_dcim_platform_id" FOREIGN KEY (parent_id) REFERENCES dcim_platform(id) DEFERRABLE INITIALLY DEFERRED
Referenced by:
    TABLE "dcim_device" CONSTRAINT "dcim_device_platform_id_468138f1_fk" FOREIGN KEY (platform_id) REFERENCES dcim_platform(id) DEFERRABLE INITIALLY DEFERRED
    TABLE "dcim_devicetype" CONSTRAINT "dcim_devicetype_default_platform_id_1f6ff6ac_fk_dcim_plat" FOREIGN KEY (default_platform_id) REFERENCES dcim_platform(id) DEFERRABLE INITIALLY DEFERRED
    TABLE "dcim_platform" CONSTRAINT "dcim_platform_parent_id_795c7101_fk_dcim_platform_id" FOREIGN KEY (parent_id) REFERENCES dcim_platform(id) DEFERRABLE INITIALLY DEFERRED
    TABLE "virtualization_virtualmachine" CONSTRAINT "virtualization_virtualmachine_platform_id_a6c5ccb2_fk" FOREIGN KEY (platform_id) REFERENCES dcim_platform(id) DEFERRABLE INITIALLY DEFERRED

Any input will be greatly appreciated!

/Erik

[donix42]

I proceeded to educate myself on how to check this and did python manage.py showmigrations which showed pretty Xs on all migrations and python manage.py migrate --check which exits cleanly.

[pheus]

I’m not using the containerized setup of NetBox myself, so I might be mistaken, but one thing stands out: why do you have a container named netbox-docker-netbox-housekeeping-1? In recent NetBox releases (v4.4+), there isn’t a separate housekeeping service anymore. If you’re seeing that container, it’s likely coming from an older Compose file or a custom image.

If you’re building the image yourself, I’d recommend:

1. Compare with the current reference Compose from the netbox-docker project and remove any housekeeping service that’s still defined.
2. Update your stack to the new scheme (e.g., ensure the current services are present and housekeeping isn’t).

Hope this helps!

[donix42]

Spot on. I was definitely unnecessarily running the housekeeping container which was deprecated. I had rather religiously read the netbox release notes and completely ignored the release notes for netbox-docker.

Should I be able to trust what python manage.py showmigrations reports as the truth regarding completeness of migrations?

[pheus]

Thanks for the follow‑up.

Should you trust python manage.py showmigrations?
Short answer: mostly yes, with caveats. Django records applied migrations in the django_migrations table, and showmigrations reflects that history for the database your command is connected to. If it reports everything as applied, that’s what Django will act on. However, it does not validate the live schema.

Given the uncertainty - and the fact that the deprecated housekeeping service was previously running - I agree with your instinct: restore from your pre‑upgrade backup and redo the upgrade cleanly. It’s the safest way to ensure a consistent and supported state.

[donix42]

Thank you for the clarification @pheus!