Netbox Migration

[Snowbull08]

Hi, I am new to Netbox, and in my new Job, we have Netbox 2.1.5 installed on Ubuntu 16. Notes from my predecessor advise that all upgrade paths weren't fruitful. Please suggest the migration path from 2.1.5 to the latest version.

[mtinberg]

You will probably need to read through the release notes for each major version from 2.1 to 2.11 to 3.4 as there may be steps you need to complete, eg. upgrade to a current version of PostgreSQL, but the major one is that 3.x doesn't include the db migration scripts from 2.x prior to 2.11.x, so you have to do a stepwise upgrade to 2.11.x first, and then you can upgrade to current. Other people who've had to refresh an older instance like this have shared some notes in this mailing list which you may be able to search for, common problems are that pip install will grab the latest of everything, but that often installs versions of dependencies than the old version of Netbox was tested against and isn't compatible with, so you have to pin an older version in requirements.txt. I would start by using the PostgreSQL tools (pg_dump) to dump the database on the old system, then install 2.11.x on a new system, get that working, then restore the old 2.1 database onto that new system and run the upgrade.sh script as documented for any upgrade. Then you can upgrade the new system to the latest Netbox and run the upgrade procedure again to get a new system with a new 3.4.x database. If you run into any problems, you can always start over and try again, as you haven't broken the existing Netbox 2.1 install you are relying on. — Mark Tinberg ***@***.***> Division of Information Technology-Network Services University of Wisconsin-Madison

…

________________________________ From: Snowbull08 ***@***.***> Sent: Monday, December 19, 2022 11:43 PM To: netbox-community/netbox ***@***.***> Cc: Subscribed ***@***.***> Subject: [netbox-community/netbox] Netbox Migration (Discussion #11253) Hi, I am new to Netbox, and in my new Job, we have Netbox 2.1.5 installed on Ubuntu 16. Notes from my predecessor advise that all upgrade paths weren't fruitful. Please suggest the migration path from 2.1.5 to the latest version. — Reply to this email directly, view it on GitHub<#11253>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AAS7UMZONX2UKXQCRXEBDMDWOFBR3ANCNFSM6AAAAAATEDOQ44>. You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>

[markkuleinio]

common problems are that pip install will grab the latest of everything, but that often installs versions of dependencies than the old version of Netbox was tested against and isn't compatible with, so you have to pin an older version in requirements.txt.

FWIW, I set up https://github.com/markkuleinio/netbox-freezes if that helps someone at some point. It only starts at NetBox 3.1.8 though.

[jeremystretch]

Please consult the official documentation rather than relying on your predecessor's notes. If you abide by the upgrade instructions carefully you're unlikely to encounter any issues.

[julianze]

It's a dependency of Markdown, which is pinned:

(venv) root@netbox:/opt/netbox# pip3 show importlib-metadata                       Name: importlib-metadata
Version: 4.6.1
Summary: Read metadata from Python packages
Home-page: https://github.com/python/importlib_metadata
Author: Jason R. Coombs
Author-email: [email protected]
License: UNKNOWN
Location: /opt/netbox/venv/lib/python3.7/site-packages
Requires: typing-extensions, zipp
Required-by: click, jsonschema, Markdown, redis
(venv) root@netbox:/opt/netbox#

[candlerb]

Hmm. Are we both talking about 2.11.12? I have importlib-metadata on 3.4.2 but not 2.11.12.

On my 2.11.12 test system:

(venv) root@netbox-test:/opt/netbox# pip freeze | egrep -i 'markdown|importlib'
importlib-resources==5.10.2
Markdown==3.3.4

On 3.4.2:

(venv) root@netbox3:/opt/netbox# pip freeze | egrep -i 'markdown|importlib'
importlib-metadata==4.13.0
importlib-resources==5.10.2
Markdown==3.3.7

[candlerb]

Ah I think I see: I'm testing with Ubuntu 20.04 / python 3.8. The dependency on importlib-metadata is only for python < 3.8.

root@netbox-test:/opt/netbox# grep Requires venv/lib/python3.8/site-packages/Markdown-3.3.4.dist-info/METADATA
Requires-Python: >=3.6
Requires-Dist: importlib-metadata ; python_version < "3.8"
Requires-Dist: coverage ; extra == 'testing'
Requires-Dist: pyyaml ; extra == 'testing'

[julianze]

I have a netbox v2.11.10 on this system:

root@netbox:~# python3 --version
Python 3.7.3
root@netbox:~# cat /etc/debian_version
10.9

[candlerb]

OK, so that's it: with python 3.7, Markdown requires importlib-metadata (any version); with python 3.8 it does not.

Therefore, another solution would be to upgrade your base python version to 3.8.

And/or you could report the dependency problem with Markdown under python 3.7 upstream. (However 3.7 is not too far from end of life - 27 Jun 2023)