NetBox v2.9.8 To v3.2.1 Upgrade Error #9252

kopacko · 2022-04-28T16:23:57Z

kopacko
Apr 28, 2022

Hello,

I have built a new Ubuntu 20.04 VM and installed NetBox. The install completed successfully and I was able to validate the new install via the web GUI.

I exported the DB from the existing NetBox VM and imported it into the new VM via this command:
sudo -u postgres psql netbox < netbox-v2.9.8-2022-04-26.sql

This completed without error.

Then I ran the upgrade.sh script and received this error.

Skipping local dependencies (local_requirements.txt not found)
Applying database migrations (python3 netbox/manage.py migrate)...
Traceback (most recent call last):
  File "/opt/netbox-3.2.1/venv/lib/python3.8/site-packages/django/db/migrations/loader.py", line 276, in build_graph
    self.graph.validate_consistency()
  File "/opt/netbox-3.2.1/venv/lib/python3.8/site-packages/django/db/migrations/graph.py", line 198, in validate_consistency
    [n.raise_error() for n in self.node_map.values() if isinstance(n, DummyNode)]
  File "/opt/netbox-3.2.1/venv/lib/python3.8/site-packages/django/db/migrations/graph.py", line 198, in <listcomp>
    [n.raise_error() for n in self.node_map.values() if isinstance(n, DummyNode)]
  File "/opt/netbox-3.2.1/venv/lib/python3.8/site-packages/django/db/migrations/graph.py", line 60, in raise_error
    raise NodeNotFoundError(self.error_message, self.key, origin=self.origin)
django.db.migrations.exceptions.NodeNotFoundError: Migration dcim.0131_consoleport_speed dependencies reference nonexistent parent node ('dcim', '0130_sitegroup')

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

Traceback (most recent call last):
  File "netbox/manage.py", line 10, in <module>
    execute_from_command_line(sys.argv)
  File "/opt/netbox-3.2.1/venv/lib/python3.8/site-packages/django/core/management/__init__.py", line 446, in execute_from_command_line
    utility.execute()
  File "/opt/netbox-3.2.1/venv/lib/python3.8/site-packages/django/core/management/__init__.py", line 440, in execute
    self.fetch_command(subcommand).run_from_argv(self.argv)
  File "/opt/netbox-3.2.1/venv/lib/python3.8/site-packages/django/core/management/base.py", line 414, in run_from_argv
    self.execute(*args, **cmd_options)
  File "/opt/netbox-3.2.1/venv/lib/python3.8/site-packages/django/core/management/base.py", line 460, in execute
    output = self.handle(*args, **options)
  File "/opt/netbox-3.2.1/venv/lib/python3.8/site-packages/django/core/management/base.py", line 98, in wrapped
    res = handle_func(*args, **kwargs)
  File "/opt/netbox-3.2.1/venv/lib/python3.8/site-packages/django/core/management/commands/migrate.py", line 108, in handle
    executor = MigrationExecutor(connection, self.migration_progress_callback)
  File "/opt/netbox-3.2.1/venv/lib/python3.8/site-packages/django/db/migrations/executor.py", line 18, in __init__
    self.loader = MigrationLoader(self.connection)
  File "/opt/netbox-3.2.1/venv/lib/python3.8/site-packages/django/db/migrations/loader.py", line 58, in __init__
    self.build_graph()
  File "/opt/netbox-3.2.1/venv/lib/python3.8/site-packages/django/db/migrations/loader.py", line 295, in build_graph
    raise NodeNotFoundError(
django.db.migrations.exceptions.NodeNotFoundError: Migration dcim.0131_consoleport_speed depends on nonexistent node ('dcim', '0130_sitegroup'). Django tried to replace migration dcim.0130_sitegroup with any of [dcim.0003_squashed_0130] but wasn't able to because some of the replaced migrations are already applied.

I am unsure what to do to get past this.

joaolucasmacedo · 2022-04-28T17:25:12Z

joaolucasmacedo
Apr 28, 2022

I suspect it is bette rto update from 2.9 to 2.11 and than to 3.0. Than you can run upgrade to 3.1 >> 3.2. It could be much more safe.
You also need to check you Python version, since Netbox 2.9 is not compatible with python 3.8 and Netbox 3.2 is only compatible with python 3.8

1 reply

jeremystretch Apr 28, 2022
Maintainer

Per the release notes, you must upgrade to v2.11 before upgrading to v3.0.

kopacko · 2022-04-28T20:11:34Z

kopacko
Apr 28, 2022
Author

Thank ya!

0 replies

kopacko · 2022-04-28T20:25:53Z

kopacko
Apr 28, 2022
Author

I am attempting to upgrade to v2.11.0 and I get this message when running upgrade.sh:

Traceback (most recent call last):
  File "netbox/manage.py", line 10, in <module>
    execute_from_command_line(sys.argv)
  File "/opt/netbox-2.11.0/venv/lib/python3.6/site-packages/django/core/management/__init__.py", line 419, in execute_from_command_line
    utility.execute()
  File "/opt/netbox-2.11.0/venv/lib/python3.6/site-packages/django/core/management/__init__.py", line 413, in execute
    self.fetch_command(subcommand).run_from_argv(self.argv)
  File "/opt/netbox-2.11.0/venv/lib/python3.6/site-packages/django/core/management/base.py", line 354, in run_from_argv
    self.execute(*args, **cmd_options)
  File "/opt/netbox-2.11.0/venv/lib/python3.6/site-packages/django/core/management/base.py", line 398, in execute
    output = self.handle(*args, **options)
  File "/opt/netbox-2.11.0/venv/lib/python3.6/site-packages/django/core/management/base.py", line 89, in wrapped
    res = handle_func(*args, **kwargs)
  File "/opt/netbox-2.11.0/venv/lib/python3.6/site-packages/django/core/management/commands/migrate.py", line 246, in handle
    fake_initial=fake_initial,
  File "/opt/netbox-2.11.0/venv/lib/python3.6/site-packages/django/db/migrations/executor.py", line 117, in migrate
    state = self._migrate_all_forwards(state, plan, full_plan, fake=fake, fake_initial=fake_initial)
  File "/opt/netbox-2.11.0/venv/lib/python3.6/site-packages/django/db/migrations/executor.py", line 147, in _migrate_all_forwards
    state = self.apply_migration(state, migration, fake=fake, fake_initial=fake_initial)
  File "/opt/netbox-2.11.0/venv/lib/python3.6/site-packages/django/db/migrations/executor.py", line 227, in apply_migration
    state = migration.apply(state, schema_editor)
  File "/opt/netbox-2.11.0/venv/lib/python3.6/site-packages/django/db/migrations/migration.py", line 126, in apply
    operation.database_forwards(self.app_label, schema_editor, old_state, project_state)
  File "/opt/netbox-2.11.0/venv/lib/python3.6/site-packages/django/db/migrations/operations/special.py", line 190, in database_forwards
    self.code(from_state.apps, schema_editor)
  File "/opt/netbox-2.11.0/netbox/extras/migrations/0051_migrate_customfields.py", line 72, in migrate_customfieldvalues
    raise e
  File "/opt/netbox-2.11.0/netbox/extras/migrations/0051_migrate_customfields.py", line 69, in migrate_customfieldvalues
    cf_data['custom_field_data'][cfv.field.name] = deserialize_value(cfv.field, cfv.serialized_value)
  File "/opt/netbox-2.11.0/netbox/extras/migrations/0051_migrate_customfields.py", line 15, in deserialize_value
    return field._choices.get(pk=int(value)).value
ValueError: invalid literal for int() with base 10: 'ATLNGABU'

2 replies

joaolucasmacedo Apr 29, 2022

Which Python version are you running?

kopacko May 2, 2022
Author

It is currently: Python 3.8.10.

kopacko · 2022-05-26T04:48:36Z

kopacko
May 26, 2022
Author

Should I step up one version at a time from v2.9.8 to get to v2.11??

7 replies

candlerb May 26, 2022

In postgres, \d or \dt will give you a list of tables. One of those is called something like extras_customfield_values (I don't remember exactly). You can search through that for the offending value.

The join to find out exactly what object that links to is rather painful, and I no longer have my old scripts to do that. You may find some info if you search the old netbox group in groups.google.com. But you may also need to find someone who is comfortable working with SQL, if you are not.

kopacko May 26, 2022
Author

This got me a little closer (I think!). I went to the python script file and looked at line 15 (where the error log shows) and found this:

def deserialize_value(field, value):
    """
    Convert serialized values to JSON equivalents.
    """
    if field.type in (CustomFieldTypeChoices.TYPE_INTEGER):
        return int(value)
    if field.type == CustomFieldTypeChoices.TYPE_BOOLEAN:
        return bool(int(value))
    if field.type == CustomFieldTypeChoices.TYPE_SELECT:
        return field._choices.get(pk=int(value)).value
    return value

When I look at that table in postgres, I don't even have a table entry with that value ATLNGABU. The values are all similar to this:

 id  |                   value                   | weight | field_id
-----+-------------------------------------------+--------+----------
   1 | 10 kVA                                    |     10 |        2
   2 | 20 kVA                                    |     20 |        2
   3 | 30 kVA                                    |     30 |        2
   4 | 40 kVA                                    |     40 |        2
   5 | 50 kVA                                    |     50 |        2
   6 | 60 kVA                                    |     60 |        2
   7 | 70 kVA                                    |     70 |        2
   8 | 80 kVA                                    |     80 |        2
   9 | 90 kVA                                    |     90 |        2
  10 | 3 kVA                                     |      3 |        2
  20 | 10th Floor                                |    100 |        3
  33 | 15 kVA                                    |     15 |        2
 439 | X10-5N                                    |   2411 |       80
  41 | 10 Meg                                    |     10 |        9
  42 | 20 Meg                                    |     20 |        9
  43 | 50 Meg                                    |     50 |        9
  44 | 100 Meg                                   |    100 |        9
  45 | 250 Meg                                   |    250 |        9
  46 | 1 Gig                                     |   1000 |        9
  47 | Cable Modem                               |      1 |       10
  48 | DSL                                       |      2 |       10

candlerb May 26, 2022

Then I gave you the wrong table name. It's one of the other extras_customfield_xxx tables that contains the values entered into text and numeric fields; I think the table you've shown gives the enumerated choices for selection fields.

kopacko May 26, 2022
Author

These are the only extras tables I see:

public | extras_configcontext                    | table | netbox
public | extras_configcontext_cluster_groups     | table | netbox
public | extras_configcontext_clusters           | table | netbox
public | extras_configcontext_platforms          | table | netbox
public | extras_configcontext_regions            | table | netbox
public | extras_configcontext_roles              | table | netbox
public | extras_configcontext_sites              | table | netbox
public | extras_configcontext_tags               | table | netbox
public | extras_configcontext_tenant_groups      | table | netbox
public | extras_configcontext_tenants            | table | netbox
public | extras_customfield                      | table | netbox
public | extras_customfield_content_types        | table | netbox
public | extras_customfieldchoice                | table | netbox
public | extras_customfieldvalue                 | table | netbox
public | extras_customlink                       | table | netbox
public | extras_exporttemplate                   | table | netbox
public | extras_imageattachment                  | table | netbox
public | extras_jobresult                        | table | netbox
public | extras_objectchange                     | table | netbox
public | extras_tag                              | table | netbox
public | extras_taggeditem                       | table | netbox
public | extras_webhook                          | table | netbox
public | extras_webhook_obj_type                 | table | netbox

candlerb May 26, 2022

I think it's extras_customfieldvalue you want. You didn't show which table you had queried previously, but I'm guessing it was extras_customfieldchoice

kopacko · 2022-05-30T14:24:53Z

kopacko
May 30, 2022
Author

@candlerb Ok so I went through all the extras tables nothing stood out as incorrect. I decided I would just upgrade to each individual version from v2.9.8. All went well for v2.9.x. When I went to v.2.10.0 I got this error:

Running migrations:
  Applying dcim.0117_custom_field_data... OK
  Applying dcim.0118_inventoryitem_mptt... OK
  Applying dcim.0119_inventoryitem_mptt_rebuild... OK
  Applying dcim.0120_cache_cable_peer...
    Updating console port cable peers...
    Updating console server port cable peers...
    Updating power port cable peers...
    Updating power outlet cable peers...
    Updating interface cable peers...
    Updating front port cable peers...
    Updating rear port cable peers...
    Updating power feed cable peers...
 OK
  Applying dcim.0121_cablepath... OK
  Applying circuits.0020_custom_field_data... OK
  Applying circuits.0021_cache_cable_peer...
    Updating circuit termination cable peers...
 OK
  Applying circuits.0022_cablepath... OK
  Applying circuits.0023_circuittermination_port_speed_optional... OK
  Applying circuits.0024_standardize_name_length... OK
  Applying dcim.0122_standardize_name_length... OK
  Applying virtualization.0018_custom_field_data... OK
  Applying tenancy.0010_custom_field_data... OK
  Applying secrets.0010_custom_field_data... OK
  Applying ipam.0038_custom_field_data... OK
  Applying extras.0048_exporttemplate_remove_template_language... OK
  Applying extras.0049_remove_graph... OK
  Applying extras.0050_customfield_changes... OK
  Applying extras.0051_migrate_customfields...Serving Wire Center (select): ATLNGABU (4791)
Traceback (most recent call last):
  File "netbox/manage.py", line 10, in <module>
    execute_from_command_line(sys.argv)
  File "/opt/netbox-2.10.0/venv/lib/python3.6/site-packages/django/core/management/__init__.py", line 401, in execute_from_command_line
    utility.execute()
  File "/opt/netbox-2.10.0/venv/lib/python3.6/site-packages/django/core/management/__init__.py", line 395, in execute
    self.fetch_command(subcommand).run_from_argv(self.argv)
  File "/opt/netbox-2.10.0/venv/lib/python3.6/site-packages/django/core/management/base.py", line 330, in run_from_argv
    self.execute(*args, **cmd_options)
  File "/opt/netbox-2.10.0/venv/lib/python3.6/site-packages/django/core/management/base.py", line 371, in execute
    output = self.handle(*args, **options)
  File "/opt/netbox-2.10.0/venv/lib/python3.6/site-packages/django/core/management/base.py", line 85, in wrapped
    res = handle_func(*args, **kwargs)
  File "/opt/netbox-2.10.0/venv/lib/python3.6/site-packages/django/core/management/commands/migrate.py", line 245, in handle
    fake_initial=fake_initial,
  File "/opt/netbox-2.10.0/venv/lib/python3.6/site-packages/django/db/migrations/executor.py", line 117, in migrate
    state = self._migrate_all_forwards(state, plan, full_plan, fake=fake, fake_initial=fake_initial)
  File "/opt/netbox-2.10.0/venv/lib/python3.6/site-packages/django/db/migrations/executor.py", line 147, in _migrate_all_forwards
    state = self.apply_migration(state, migration, fake=fake, fake_initial=fake_initial)
  File "/opt/netbox-2.10.0/venv/lib/python3.6/site-packages/django/db/migrations/executor.py", line 227, in apply_migration
    state = migration.apply(state, schema_editor)
  File "/opt/netbox-2.10.0/venv/lib/python3.6/site-packages/django/db/migrations/migration.py", line 124, in apply
    operation.database_forwards(self.app_label, schema_editor, old_state, project_state)
  File "/opt/netbox-2.10.0/venv/lib/python3.6/site-packages/django/db/migrations/operations/special.py", line 190, in database_forwards
    self.code(from_state.apps, schema_editor)
  File "/opt/netbox-2.10.0/netbox/extras/migrations/0051_migrate_customfields.py", line 72, in migrate_customfieldvalues
    raise e
  File "/opt/netbox-2.10.0/netbox/extras/migrations/0051_migrate_customfields.py", line 69, in migrate_customfieldvalues
    cf_data['custom_field_data'][cfv.field.name] = deserialize_value(cfv.field, cfv.serialized_value)
  File "/opt/netbox-2.10.0/netbox/extras/migrations/0051_migrate_customfields.py", line 15, in deserialize_value
    return field._choices.get(pk=int(value)).value
ValueError: invalid literal for int() with base 10: 'ATLNGABU'

Here are the two lines that stood out:

Applying extras.0051_migrate_customfields...Serving Wire Center (select): ATLNGABU (4791)

ValueError: invalid literal for int() with base 10: 'ATLNGABU'

I assume the "Serving Wire Center" option is where the issue is. So I went back to v2.9.11 and worked my way through the circuits until I found this error:

<class 'ValueError'>

invalid literal for int() with base 10: 'ATLNGABU'

Python version: 3.6.9
NetBox version: 2.9.11

I went to sql export and found this section:

COPY public.circuits_circuit (id, created, last_updated, cid, install_date, commit_rate, comments, provider_id, type_id, tenant_id, description, status) FROM stdin;
1	2016-09-14	2018-10-15 19:37:34.465159+00	XXXX.123456 ATI	2015-02-03	50000		1	1	43		active
53	2016-10-14	2018-10-15 19:36:13.409707+00	XXXX.123456 ATI	2014-10-17	50000		1	1	43		active
29	2016-10-14	2018-10-15 19:45:35.617759+00	XXXX.123456 ATI	2016-03-01	50000		1	1	43		active
17	2016-10-14	2018-10-15 19:45:21.311752+00	XXXX.123456 ATI	2014-11-19	50000		1	1	43		active

I removed most off the entries in the table and changed the circuit IDs above for obvious reasons, but the error comes from entry #1 in this list. I checked a little over a 100 entries without issue, only the entry related to #1 seems to be the issue but I cannot see where or what the issue is mad about. I am not sure exactly which column, in the table entry it is checking either as entry #1 does not even have the text ATLNGABU.

0 replies

kopacko · 2022-05-30T15:18:21Z

kopacko
May 30, 2022
Author

@candlerb So after digging through all my various custom fields, the section that was generating this error was missing an entry for ATLNGABU. So I recreated it, then edited the circuit to reference it, and was able to upgrade to v2.10.0 now.

0 replies

kopacko · 2022-05-30T16:14:00Z

kopacko
May 30, 2022
Author

I got fully upgraded to v2.11.12 without issue. I then tried to upgrade to v3.0.0 and I get this error:

# sudo -H /opt/netbox/upgrade.sh

Removing old virtual environment...
Creating a new virtual environment at /opt/netbox-3.0.0/venv...
Error: Command '['/opt/netbox-3.0.0/venv/bin/python3', '-Im', 'ensurepip', '--upgrade', '--default-pip']' returned non-zero exit status 1.
--------------------------------------------------------------------
ERROR: Failed to create the virtual environment. Check that you have
the required system packages installed and the following path is
writable: /opt/netbox-3.0.0/venv
--------------------------------------------------------------------

My python version is:

# python3 -V
Python 3.8.13

I am unsure what to do from here.

1 reply

candlerb May 30, 2022

I suggest you edit /opt/netbox/upgrade.sh, add set -x as the first line after the shebang line, and run it again. It will show the shell commands it's executing.

The string "ensurepip" does not appear anywhere in the source code of Netbox 3.2.3, or Netbox 3.0.0, so my guess is it's failing here:

${PYTHON} -m venv ${VIRTUALENV}

The problem might be to do with having multiple versions of python/python3 on your system. To force a specific one, you can do something like this:

PYTHON=/usr/bin/python3.8 sudo -HE ./upgrade.sh

Or it might be that the filesystem really isn't writeable. You could try running the command itself directly in the shell, and see if you get a clearer error:

sudo -H /opt/netbox-3.0.0/venv/bin/python3 -Im ensurepip --upgrade --default-pip

kopacko · 2022-05-30T17:35:18Z

kopacko
May 30, 2022
Author

Here's the output:

# PYTHON=/usr/bin/python3.8 sudo -HE /opt/netbox/upgrade.sh
++ dirname /opt/netbox/upgrade.sh
+ cd /opt/netbox
++ pwd -P
+ VIRTUALENV=/opt/netbox-3.0.0/venv
+ PYTHON=/usr/bin/python3.8
+ '[' -d /opt/netbox-3.0.0/venv ']'
+ COMMAND='rm -rf /opt/netbox-3.0.0/venv'
+ echo 'Removing old virtual environment...'
Removing old virtual environment...
+ eval rm -rf /opt/netbox-3.0.0/venv
++ rm -rf /opt/netbox-3.0.0/venv
+ COMMAND='/usr/bin/python3.8 -m venv /opt/netbox-3.0.0/venv'
+ echo 'Creating a new virtual environment at /opt/netbox-3.0.0/venv...'
Creating a new virtual environment at /opt/netbox-3.0.0/venv...
+ eval /usr/bin/python3.8 -m venv /opt/netbox-3.0.0/venv
++ /usr/bin/python3.8 -m venv /opt/netbox-3.0.0/venv
Error: Command '['/opt/netbox-3.0.0/venv/bin/python3.8', '-Im', 'ensurepip', '--upgrade', '--default-pip']' returned non-zero exit status 1.
+ echo --------------------------------------------------------------------
--------------------------------------------------------------------
+ echo 'ERROR: Failed to create the virtual environment. Check that you have'
ERROR: Failed to create the virtual environment. Check that you have
+ echo 'the required system packages installed and the following path is'
the required system packages installed and the following path is
+ echo 'writable: /opt/netbox-3.0.0/venv'
writable: /opt/netbox-3.0.0/venv
+ echo --------------------------------------------------------------------
--------------------------------------------------------------------
+ exit 1

I checked and even set the perms for the venv folder to 777 and got the same error.

1 reply

markkuleinio May 30, 2022

In my test system that does not have python3-venv package (which is listed in NetBox installation guide) installed:

$ python3 -m venv venv
The virtual environment was not created successfully because ensurepip is not
available.  On Debian/Ubuntu systems, you need to install the python3-venv
package using the following command.

    apt-get install python3-venv

You may need to use sudo with that command.  After installing the python3-venv
package, recreate your virtual environment.

Failing command: ['/home/markku/venv/bin/python3', '-Im', 'ensurepip', '--upgrade', '--default-pip']

Have you installed it?

kopacko · 2022-05-30T19:47:13Z

kopacko
May 30, 2022
Author

Yes I have it installed, this is not a new install.

I have been using this same box now for years. I am just doing upgrades to get to the latest version.

# sudo apt-get install python3-venv

Reading package lists... Done
Building dependency tree
Reading state information... Done
python3-venv is already the newest version (3.6.7-1~18.04).
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.

1 reply

markkuleinio May 31, 2022

Wait, you seem to have the venv activated while you were running upgrade.sh:

Error: Command '['/opt/netbox-3.0.0/venv/bin/python3',

Deactivate the venv before running the upgrade script.

kopacko · 2022-05-31T13:59:53Z

kopacko
May 31, 2022
Author

@markkuleinio Ok....I thought it was doing that automatically via this line:

rm -rf /opt/netbox-3.0.0/venv

I will do it manually first and report back.

0 replies

kopacko · 2022-05-31T14:10:26Z

kopacko
May 31, 2022
Author

I was not able to get into the virtual environment. I got this error:

#: source /opt/netbox/venv/bin/activate
bash: /opt/netbox/venv/bin/activate: No such file or directory

When I checked the venv directory, this is all I see:

/opt/netbox/venv/bin#: ls -al
total 8
drwxr-xr-x 2 root root 4096 May 30 17:34 .
drwxr-xr-x 5 root root 4096 May 30 17:34 ..
lrwxrwxrwx 1 root root    9 May 30 17:34 python -> python3.8
lrwxrwxrwx 1 root root    9 May 30 17:34 python3 -> python3.8
lrwxrwxrwx 1 root root   18 May 30 17:34 python3.8 -> /usr/bin/python3.8

Not being familiar with virtual environments, I am not sure I know how to see if any are actively running.

2 replies

markkuleinio May 31, 2022

If you are unsure if you have the venv activated or not (your prompt should indicate it), just say deactivate and you are good to go: run upgrade.sh, it will remove the venv if it already exists.

markkuleinio May 31, 2022

But can you show the outputs of dpkg -l python3-venv and python3 -m venv /tmp/venv?

kopacko · 2022-05-31T14:56:53Z

kopacko
May 31, 2022
Author

Here you go:

:~# dpkg -l python3-venv
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name                                         Version                     Architecture                Description
+++-============================================-===========================-===========================-=============================================================================================
ii  python3-venv                                 3.6.7-1~18.04               amd64                       pyvenv-3 binary for python3 (default python3 version)

:~# python3 -m venv /tmp/venv
Error: Command '['/tmp/venv/bin/python3', '-Im', 'ensurepip', '--upgrade', '--default-pip']' returned non-zero exit status 1.

1 reply

candlerb May 31, 2022

Somehow you have got python3 3.8 but python3-venv 3.6.

If this is Ubuntu 18.04, then "apt-get install python3.8 python3.8-venv" and this will give you the necessary pieces. But you need to do

PYTHON=python3.8 ./upgrade.sh

whenever you run upgrade.sh.

markkuleinio · 2022-05-31T15:02:10Z

markkuleinio
May 31, 2022

I have built a new Ubuntu 20.04 VM and installed NetBox.
ii python3-venv 3.6.7-1~18.04

How is it possible that on a new Ubuntu 20.04 you have an outdated Python 3.6 installed?

Sorry, I believe I cannot help you with this, I have never installed NetBox on a server using non-system default Python, someone else probably has better ideas.

0 replies

kopacko · 2022-05-31T15:05:58Z

kopacko
May 31, 2022
Author

At the moment, I am trying to in-place upgrade the existing Netbox server on 18.04. My thought was, get the SQL db to where it can be imported into the new 20.04 VM with Netbox.

1 reply

markkuleinio May 31, 2022

If I was in your position (old server + old NetBox), I would definitely do all the NetBox upgrade phases in the new server (so that I could always easily start from scratch again in case of problems) and leave the old server alone.

kopacko · 2022-05-31T15:36:20Z

kopacko
May 31, 2022
Author

Yea, I'm already into the upgrades on the existing box. I've made to v2.11.12, I am just trying to get over the 3.0 upgrade now.

0 replies

kopacko · 2022-05-31T21:58:44Z

kopacko
May 31, 2022
Author

@candlerb & @markkuleinio

I want to thank you both for all the help. I have successfully moved past another issue and was able to load version v3.1.0. I have done a SQL backup and will be continuing the upgrades to get to the latest and greatest.

Then hopefully, a simple SQL export and import into the new server and all will be well.

0 replies

kopacko · 2022-06-01T14:44:40Z

kopacko
Jun 1, 2022
Author

@candlerb & @markkuleinio

Now that I have a working copy of Netbox on v3.1.0. Would you suggest I export the DB and build out v3.1.0 on the new server to continue the upgrades?

1 reply

candlerb Jun 1, 2022

I would:

Install v3.2.4 on the new server (*). Test it works
Dump the database from v3.1.0 and import it into the new server (as well as any media, scripts, reports etc)
Run './upgrade.sh' on the new server, so that it will perform the database migrations

(*) Remember to make all the right changes to configuration.py. Starting with a clean one based on configuration.example.py is a good idea, if your existing one has become old and crufty.

kopacko · 2022-06-02T16:49:44Z

kopacko
Jun 2, 2022
Author

@candlerb

Very happy to report that the upgrade to v3.2.4 was successful. I probably need to go thru some of the sites/devices/etc data and validate but after an initial look, all seems to be well!

0 replies

kopacko · 2022-06-03T14:24:43Z

kopacko
Jun 3, 2022
Author

FYI, this post can be closed. Again thank you all for the help.

0 replies

NetBox v2.9.8 To v3.2.1 Upgrade Error #9252

Uh oh!

Uh oh!

Replies: 19 comments · 18 replies

Uh oh!

Uh oh!

jeremystretch Apr 28, 2022 Maintainer

Uh oh!

kopacko Apr 28, 2022 Author

Uh oh!

kopacko Apr 28, 2022 Author

Uh oh!

Uh oh!

kopacko May 2, 2022 Author

Uh oh!

kopacko May 26, 2022 Author

Uh oh!

Uh oh!

kopacko May 26, 2022 Author

Uh oh!

Uh oh!

kopacko May 26, 2022 Author

Uh oh!

Uh oh!

kopacko May 30, 2022 Author

Uh oh!

kopacko May 30, 2022 Author

Uh oh!

kopacko May 30, 2022 Author

Uh oh!

Uh oh!

kopacko May 30, 2022 Author

Uh oh!

Uh oh!

Uh oh!

kopacko May 30, 2022 Author

Uh oh!

Uh oh!

kopacko May 31, 2022 Author

Uh oh!

kopacko May 31, 2022 Author

Uh oh!

Uh oh!

Uh oh!

Uh oh!

kopacko May 31, 2022 Author

Uh oh!

Uh oh!

Uh oh!

kopacko May 31, 2022 Author

Uh oh!

Uh oh!

kopacko May 31, 2022 Author

Uh oh!

kopacko May 31, 2022 Author

Uh oh!

Replies: 19 comments 18 replies

jeremystretch Apr 28, 2022
Maintainer

kopacko
Apr 28, 2022
Author

kopacko
Apr 28, 2022
Author

kopacko May 2, 2022
Author

kopacko
May 26, 2022
Author

kopacko May 26, 2022
Author

kopacko May 26, 2022
Author

kopacko
May 30, 2022
Author

kopacko
May 30, 2022
Author

kopacko
May 30, 2022
Author

kopacko
May 30, 2022
Author

kopacko
May 30, 2022
Author

kopacko
May 31, 2022
Author

kopacko
May 31, 2022
Author

kopacko
May 31, 2022
Author

kopacko
May 31, 2022
Author

kopacko
May 31, 2022
Author

kopacko
May 31, 2022
Author