Netbox-floorplan-plugin on Netbox v4.4.5 - errors during install.

[sk5m7rkkyy-eng]

I've upgraded to Netbox 4.4.5 and I've tried to install the netbox-floorplan-plugin but it seems to fail during the database migrate phase, I can't be sure the fail is as a result of something that's changed in netbox or the plugin now needs attention?

My assumption is the latter of the two above, but I wonder if anyone else has been able to use the floorplan plugin with the latest netbox?

The error I think implys a table is missing. psycopg.errors.UndefinedTable: relation "netbox_floorplan_floorplan" does not exist

I've tried adding to local_requirements.txt file, updating the configuration.py and running upgrade.sh to effectively rebuild the netbox install, and the below occurs, if I remove netbox-floorplan-plugin from the configuration.py and re-run the upgrade.sh it all goes through smoothly.

(venv) root@netboxserver1:/opt/netbox/netbox# pip install netbox-floorplan-plugin
Requirement already satisfied: netbox-floorplan-plugin in /opt/netbox/venv/lib/python3.12/site-packages (0.8.0)
(venv) root@netboxserver1:/opt/netbox/netbox# pip install netbox-floorplan-plugin --force
Collecting netbox-floorplan-plugin
  Using cached netbox_floorplan_plugin-0.8.0-py3-none-any.whl.metadata (2.5 kB)
Using cached netbox_floorplan_plugin-0.8.0-py3-none-any.whl (171 kB)
Installing collected packages: netbox-floorplan-plugin
  Attempting uninstall: netbox-floorplan-plugin
    Found existing installation: netbox-floorplan-plugin 0.8.0
    Uninstalling netbox-floorplan-plugin-0.8.0:
      Successfully uninstalled netbox-floorplan-plugin-0.8.0
Successfully installed netbox-floorplan-plugin-0.8.0
(venv) root@netboxserver1:/opt/netbox/netbox# python3 manage.py migrate netbox_floorplan
Operations to perform:
  Apply all migrations: netbox_floorplan
Running migrations:
  Applying netbox_floorplan.0012_alter_floorplan_options_and_more...Traceback (most recent call last):
  File "/opt/netbox/venv/lib/python3.12/site-packages/django/db/backends/utils.py", line 103, in _execute
    return self.cursor.execute(sql)
           ^^^^^^^^^^^^^^^^^^^^^^^^
  File "/opt/netbox/venv/lib/python3.12/site-packages/psycopg/cursor.py", line 97, in execute
    raise ex.with_traceback(None)
psycopg.errors.UndefinedTable: relation "netbox_floorplan_floorplan" does not exist

The above exception was the direct cause of the following exception:

Traceback (most recent call last):
  File "/opt/netbox/netbox/manage.py", line 10, in <module>
    execute_from_command_line(sys.argv)
  File "/opt/netbox/venv/lib/python3.12/site-packages/django/core/management/__init__.py", line 442, in execute_from_command_line
    utility.execute()
  File "/opt/netbox/venv/lib/python3.12/site-packages/django/core/management/__init__.py", line 436, in execute
    self.fetch_command(subcommand).run_from_argv(self.argv)
  File "/opt/netbox/venv/lib/python3.12/site-packages/django/core/management/base.py", line 416, in run_from_argv
    self.execute(*args, **cmd_options)
  File "/opt/netbox/venv/lib/python3.12/site-packages/django/core/management/base.py", line 460, in execute
    output = self.handle(*args, **options)
             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/opt/netbox/venv/lib/python3.12/site-packages/django/core/management/base.py", line 107, in wrapper
    res = handle_func(*args, **kwargs)
          ^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/opt/netbox/venv/lib/python3.12/site-packages/django/core/management/commands/migrate.py", line 353, in handle
    post_migrate_state = executor.migrate(
                         ^^^^^^^^^^^^^^^^^
  File "/opt/netbox/venv/lib/python3.12/site-packages/django/db/migrations/executor.py", line 135, in migrate
    state = self._migrate_all_forwards(
            ^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/opt/netbox/venv/lib/python3.12/site-packages/django/db/migrations/executor.py", line 167, in _migrate_all_forwards
    state = self.apply_migration(
            ^^^^^^^^^^^^^^^^^^^^^
  File "/opt/netbox/venv/lib/python3.12/site-packages/django/db/migrations/executor.py", line 255, in apply_migration
    state = migration.apply(state, schema_editor)
            ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/opt/netbox/venv/lib/python3.12/site-packages/django/db/migrations/migration.py", line 132, in apply
    operation.database_forwards(
  File "/opt/netbox/venv/lib/python3.12/site-packages/django/db/migrations/operations/fields.py", line 174, in database_forwards
    schema_editor.remove_field(
  File "/opt/netbox/venv/lib/python3.12/site-packages/django/db/backends/base/schema.py", line 829, in remove_field
    self.execute(sql)
  File "/opt/netbox/venv/lib/python3.12/site-packages/django/db/backends/postgresql/schema.py", line 48, in execute
    return super().execute(sql, None)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/opt/netbox/venv/lib/python3.12/site-packages/django/db/backends/base/schema.py", line 204, in execute
    cursor.execute(sql, params)
  File "/opt/netbox/venv/lib/python3.12/site-packages/django/db/backends/utils.py", line 79, in execute
    return self._execute_with_wrappers(
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/opt/netbox/venv/lib/python3.12/site-packages/django/db/backends/utils.py", line 92, in _execute_with_wrappers
    return executor(sql, params, many, context)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/opt/netbox/venv/lib/python3.12/site-packages/django/db/backends/utils.py", line 100, in _execute
    with self.db.wrap_database_errors:
  File "/opt/netbox/venv/lib/python3.12/site-packages/django/db/utils.py", line 91, in __exit__
    raise dj_exc_value.with_traceback(traceback) from exc_value
  File "/opt/netbox/venv/lib/python3.12/site-packages/django/db/backends/utils.py", line 103, in _execute
    return self.cursor.execute(sql)

[pheus]

Hi there! Thanks for opening the thread, and sorry you’re running into this.

From the traceback it doesn’t look like a NetBox core or plugin bug. Django is trying to apply 0012_alter_floorplan_options_and_more (the 12th migration), which means it believes migrations 0001–0011 are already applied. However, the error indicates the underlying database table is missing. That usually means the migration history is out of sync with the actual schema - for example, the plugin was installed previously, and the plugin's tables were dropped manually without resetting migration records.

How to confirm
Run: python manage.py showmigrations netbox_floorplan
This will show which migrations Django thinks are applied for the plugin.

How to fix (typical path)

1. Back up your database first.
2. Reset the plugin’s migration state (without touching the database) so Django knows it needs to recreate the tables:
   python manage.py migrate netbox_floorplan zero --fake
3. Re‑apply the plugin migrations so the missing tables are created:
   python manage.py migrate netbox_floorplan

If this is a brand‑new install, also make sure the plugin is listed in PLUGINS in your NetBox configuration and then run python manage.py migrate so everything is applied cleanly.

⚠️ Notes:

• Use --database <name> if you’re not on the default DB.
• Avoid manually deleting rows in django_migrations unless you know exactly what you’re doing.
• Run these steps during a maintenance window if this is a production system.

Hope that helps! If you still hit issues, sharing the output of showmigrations along with your previous NetBox and plugin versions will make it easier to pinpoint the next step.

[sk5m7rkkyy-eng]

hi Pheus,

I ran the cmds you provided, the fake process completed zeroing out the migration activities, when I can to runing the migrate process again it fails at step one.

I think I've used this pluging in the distant past when I first started using netbox which could explain the bumps, there's no valuable data in that module right now so could I remove the tables it uses or would that cause more trouble?

Running migrations:
  Applying netbox_floorplan.0001_initial...Traceback (most recent call last):
  File "/opt/netbox/venv/lib/python3.12/site-packages/django/db/backends/utils.py", line 103, in _execute
    return self.cursor.execute(sql)
           ^^^^^^^^^^^^^^^^^^^^^^^^
  File "/opt/netbox/venv/lib/python3.12/site-packages/psycopg/cursor.py", line 97, in execute
    raise ex.with_traceback(None)
psycopg.errors.DuplicateTable: relation "netbox_floorplan_floorplan" already exists

The above exception was the direct cause of the following exception:

Traceback (most recent call last):
  File "/opt/netbox/netbox/manage.py", line 10, in <module>
    execute_from_command_line(sys.argv)
  File "/opt/netbox/venv/lib/python3.12/site-packages/django/core/management/__init__.py", line 442, in execute_from_command_line
    utility.execute()
  File "/opt/netbox/venv/lib/python3.12/site-packages/django/core/management/__init__.py", line 436, in execute
    self.fetch_command(subcommand).run_from_argv(self.argv)
  File "/opt/netbox/venv/lib/python3.12/site-packages/django/core/management/base.py", line 416, in run_from_argv
    self.execute(*args, **cmd_options)
  File "/opt/netbox/venv/lib/python3.12/site-packages/django/core/management/base.py", line 460, in execute
    output = self.handle(*args, **options)
             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/opt/netbox/venv/lib/python3.12/site-packages/django/core/management/base.py", line 107, in wrapper
    res = handle_func(*args, **kwargs)
          ^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/opt/netbox/venv/lib/python3.12/site-packages/django/core/management/commands/migrate.py", line 353, in handle
    post_migrate_state = executor.migrate(
                         ^^^^^^^^^^^^^^^^^
  File "/opt/netbox/venv/lib/python3.12/site-packages/django/db/migrations/executor.py", line 135, in migrate
    state = self._migrate_all_forwards(
            ^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/opt/netbox/venv/lib/python3.12/site-packages/django/db/migrations/executor.py", line 167, in _migrate_all_forwards
    state = self.apply_migration(
            ^^^^^^^^^^^^^^^^^^^^^
  File "/opt/netbox/venv/lib/python3.12/site-packages/django/db/migrations/executor.py", line 255, in apply_migration
    state = migration.apply(state, schema_editor)
            ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/opt/netbox/venv/lib/python3.12/site-packages/django/db/migrations/migration.py", line 132, in apply
    operation.database_forwards(
  File "/opt/netbox/venv/lib/python3.12/site-packages/django/db/migrations/operations/models.py", line 97, in database_forwards
    schema_editor.create_model(model)
  File "/opt/netbox/venv/lib/python3.12/site-packages/django/db/backends/base/schema.py", line 512, in create_model
    self.execute(sql, params or None)
  File "/opt/netbox/venv/lib/python3.12/site-packages/django/db/backends/postgresql/schema.py", line 45, in execute
    return super().execute(sql, params)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/opt/netbox/venv/lib/python3.12/site-packages/django/db/backends/base/schema.py", line 204, in execute
    cursor.execute(sql, params)
  File "/opt/netbox/venv/lib/python3.12/site-packages/django/db/backends/utils.py", line 79, in execute
    return self._execute_with_wrappers(
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/opt/netbox/venv/lib/python3.12/site-packages/django/db/backends/utils.py", line 92, in _execute_with_wrappers
    return executor(sql, params, many, context)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/opt/netbox/venv/lib/python3.12/site-packages/django/db/backends/utils.py", line 100, in _execute
    with self.db.wrap_database_errors:
  File "/opt/netbox/venv/lib/python3.12/site-packages/django/db/utils.py", line 91, in __exit__
    raise dj_exc_value.with_traceback(traceback) from exc_value
  File "/opt/netbox/venv/lib/python3.12/site-packages/django/db/backends/utils.py", line 103, in _execute
    return self.cursor.execute(sql)
           ^^^^^^^^^^^^^^^^^^^^^^^^
  File "/opt/netbox/venv/lib/python3.12/site-packages/psycopg/cursor.py", line 97, in execute
    raise ex.with_traceback(None)
django.db.utils.ProgrammingError: relation "netbox_floorplan_floorplan" already exists
(venv) root@netboxserver1:/opt/netbox/netbox# 

[pheus]

Hi there! Thanks for trying those commands and for sharing the error message.

psycopg.errors.DuplicateTable: relation "netbox_floorplan_floorplan" already exists means the plugin’s tables are still present in the database, but the migration history was reset to zero with --fake. In that state, Django tries to run the initial migration (0001) and create tables that already exist, hence the duplicate-table error.

You’ve got two good ways forward:

---

Option 1: Start clean by dropping the plugin tables via migrations (destructive)

Since you mentioned there’s no valuable data in this module, a clean reset can be simpler and safer than manual DROP TABLE:

1. Back up your database.
2. Mark all plugin migrations as applied (without touching the DB), so you can roll them back for real:

   python manage.py migrate netbox_floorplan --fake
   

3. Now unapply everything to drop the plugin’s tables using the migration reverses:

   python manage.py migrate netbox_floorplan zero
   

4. Recreate everything fresh:

   python manage.py migrate netbox_floorplan
   

---

Option 2: Full removal / reinstall

Follow the official NetBox docs for plugin removal (there are a few steps beyond just dropping tables):
https://netboxlabs.com/docs/netbox/plugins/removal/

After removal, reinstall and enable the plugin, then run:

python manage.py migrate

Notes

• Ensure the plugin is listed in PLUGINS so Django can discover its migrations.
• Avoid manual DROP TABLE unless absolutely necessary; migrations keep schema state consistent.

If you can share the output of:

python manage.py showmigrations netbox_floorplan

[sk5m7rkkyy-eng]

Thankyou Pheus,

I tried option1 and the scripts went through ok, but when trying to use the floorplan in Netbox it threw database errors.

I then went with option 2 and fully reinstalled the plugin and I'm up and running.