dumpdata broken looking for table extras_script #4071

New Issue

adam · 2025-12-29T18:32:57+01:00

adam commented

2025-12-29 18:32:57 +01:00

Originally created by @nniehoff on GitHub (Sep 3, 2020).

Environment

Python version: 3.8.2
NetBox version: 2.9.2

Steps to Reproduce

Install Netbox (or use docker-compose from the netbox-docker project), I followed the docs and got to the point at which I could log in to the UI to test. It was not necessary to create any objects in the DB.
Run:

python manage.py dumpdata --format yaml --traceback

Expected Behavior

Data to be output to stdout in yaml format. NOTE: without the --format yaml argument, json is output to stdout however the error still occurs.

Observed Behavior

When trying to use the dumpdata command to get a current dump of the database I get the following error:

Traceback (most recent call last):
  File "/opt/netbox/venv/lib/python3.8/site-packages/django/db/backends/utils.py", line 84, in _execute
    return self.cursor.execute(sql, params)
psycopg2.errors.UndefinedTable: relation "extras_script" does not exist
LINE 1: ...OR WITH HOLD FOR SELECT "extras_script"."id" FROM "extras_sc...
                                                             ^

For the full traceback see https://pastebin.com/pjk7zFh2

Originally created by @nniehoff on GitHub (Sep 3, 2020).  ### Environment * Python version: 3.8.2 * NetBox version: 2.9.2  ### Steps to Reproduce 1. Install Netbox (or use docker-compose from the netbox-docker project), I followed the docs and got to the point at which I could log in to the UI to test. It was not necessary to create any objects in the DB. 2. Run: ``` python manage.py dumpdata --format yaml --traceback ```  ### Expected Behavior Data to be output to stdout in yaml format. NOTE: without the `--format yaml` argument, json is output to stdout however the error still occurs.  ### Observed Behavior When trying to use the dumpdata command to get a current dump of the database I get the following error: ``` Traceback (most recent call last): File "/opt/netbox/venv/lib/python3.8/site-packages/django/db/backends/utils.py", line 84, in _execute return self.cursor.execute(sql, params) psycopg2.errors.UndefinedTable: relation "extras_script" does not exist LINE 1: ...OR WITH HOLD FOR SELECT "extras_script"."id" FROM "extras_sc... ^ ``` For the full traceback see https://pastebin.com/pjk7zFh2

adam added the type: bug label 2025-12-29 18:32:57 +01:00

adam closed this issue

2025-12-29 18:32:57 +01:00

adam commented

2025-12-29 18:32:58 +01:00

@jeremystretch commented on GitHub (Sep 4, 2020):

As a workaround, you can exclude these models when running dumpdata:

python manage.py dumpdata --format yaml --traceback -o netbox.yaml --exclude extras.Script --exclude extras.Report

@jeremystretch commented on GitHub (Sep 4, 2020): As a workaround, you can exclude these models when running `dumpdata`: ``` python manage.py dumpdata --format yaml --traceback -o netbox.yaml --exclude extras.Script --exclude extras.Report ```

adam commented

2025-12-29 18:32:58 +01:00

@nniehoff commented on GitHub (Sep 4, 2020):

@jeremystretch thanks, confirmed the workaround

@nniehoff commented on GitHub (Sep 4, 2020): @jeremystretch thanks, confirmed the workaround

adam commented

2025-12-29 18:32:58 +01:00

@jeremystretch commented on GitHub (Sep 23, 2020):

Short of hijacking Django's dumpdata management command, I don't think we can do much about this. The Report and Script models are designated as "unmanaged" because they don't actually exist in the database but still need to generate content types and permissions. AFAIK changing them to proxy or abstract won't work for this, and Django has decided not to exclude unmanaged models when dumping data.

I'm going to close this out as it seems the workaround mentioned above should suffice.

@jeremystretch commented on GitHub (Sep 23, 2020): Short of hijacking Django's `dumpdata` management command, I don't think we can do much about this. The Report and Script models are designated as "unmanaged" because they don't actually exist in the database but still need to generate content types and permissions. AFAIK changing them to proxy or abstract won't work for this, and Django has [decided not to exclude unmanaged models](https://code.djangoproject.com/ticket/13816) when dumping data. I'm going to close this out as it seems the workaround mentioned above should suffice.

Sign in to join this conversation.

Branches Tags

main

update-changelog-comments-docs

feature-removal-issue-type

20911-dropdown

20239-plugin-menu-classes-mutable-state

21097-graphql-id-lookups

feature

fix_module_substitution

20923-dcim-templates

20044-elevation-stuck-lightmode

feature-ip-prefix-link

v4.5-beta1-release

20068-import-moduletype-attrs

20766-fix-german-translation-code-literals

20378-del-script

7604-filter-modifiers-v3

circuit-swap

12318-case-insensitive-uniqueness

20637-improve-device-q-filter

20660-script-load

19724-graphql

20614-update-ruff

14884-script

02496-max-page

19720-macaddress-interface-generic-relation

19408-circuit-terminations-export-templates

20203-openapi-check

fix-19669-api-image-download

7604-filter-modifiers

19275-fixes-interface-bulk-edit

fix-17794-get_field_value_return_list

11507-show-aggregate-and-rir-on-api

9583-add_column_specific_search_field_to_tables

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: starred/netbox#4071