starred/netbox
1
0
Fork 0
mirror of https://github.com/netbox-community/netbox.git synced 2026-01-12 05:20:31 +01:00
Code Issues 273 Packages Projects Releases 10 Wiki Activity

Mention that directly upgrading from <2.11 to >3.0 is not supported #6346

New Issue
Closed
opened 2025-12-29 19:39:42 +01:00 by adam · 3 comments
adam commented 2025-12-29 19:39:42 +01:00
Owner
Copy Link

Originally created by @timon-michel-scopevisio on GitHub (Apr 13, 2022).

Change Type

Addition

Area

Installation instructions

Proposed Changes

Title says it all.
Would be very helpful to know, i just screwed up a database because of not knowing this.

Originally created by @timon-michel-scopevisio on GitHub (Apr 13, 2022). ### Change Type Addition ### Area Installation instructions ### Proposed Changes Title says it all. Would be very helpful to know, i just screwed up a database because of not knowing this.
adam added the type: documentation label 2025-12-29 19:39:42 +01:00
adam closed this issue 2025-12-29 19:39:42 +01:00
adam commented 2025-12-29 19:39:43 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Apr 14, 2022):

The first line of the upgrade instructions reads:

Prior to upgrading your NetBox instance, be sure to carefully review all release notes that have been published since your current version was released.

This link leads you to the release notes for v3.0, which starts with the following warning:

Upgrading an existing NetBox deployment to version 3.0 must be done from version 2.11.0 or later. If attempting to upgrade a deployment of NetBox v2.10 or earlier, first upgrade to a NetBox v2.11 release, and then upgrade from v2.11 to v3.0.

I'm afraid your experience highlights the importance of consulting the release notes before beginning an upgrade.

@jeremystretch commented on GitHub (Apr 14, 2022): The first line of the [upgrade instructions](https://netbox.readthedocs.io/en/stable/installation/upgrading/) reads: > Prior to upgrading your NetBox instance, be sure to carefully review all [release notes](https://netbox.readthedocs.io/en/stable/release-notes/) that have been published since your current version was released. This link leads you to the [release notes for v3.0](https://netbox.readthedocs.io/en/stable/release-notes/version-3.0/#v300-2021-08-30), which starts with the following warning: > Upgrading an existing NetBox deployment to version 3.0 **must** be done from version 2.11.0 or later. If attempting to upgrade a deployment of NetBox v2.10 or earlier, first upgrade to a NetBox v2.11 release, and then upgrade from v2.11 to v3.0. I'm afraid your experience highlights the importance of consulting the release notes before beginning an upgrade.
adam commented 2025-12-29 19:39:43 +01:00
Author
Owner
Copy Link

@timon-michel-scopevisio commented on GitHub (Apr 14, 2022):

I've read the release notes and it's not there: https://netbox.readthedocs.io/en/stable/release-notes/

You can only find it, if you read whole release notes, which is very, very time consuming.

I agree with you that the information is somewhere, but it is not intuitive. Why make it that hard to find?

@timon-michel-scopevisio commented on GitHub (Apr 14, 2022): I've read the release notes and it's not there: https://netbox.readthedocs.io/en/stable/release-notes/ You can only find it, if you read whole release notes, which is very, very time consuming. I agree with you that the information is somewhere, but it is not intuitive. Why make it that hard to find?
adam commented 2025-12-29 19:39:43 +01:00
Author
Owner
Copy Link

@ryanmerolle commented on GitHub (Apr 14, 2022):

I've read the release notes and it's not there: https://netbox.readthedocs.io/en/stable/release-notes/

Its mention in the release notes for 3.0.0. You mentioned you read the release-notes section, but you missed it at the top of the release-notes for 3.0.0? Here is the blurb:

WARNING: Upgrading an existing NetBox deployment to version 3.0 must be done from version 2.11.0 or later. If attempting to upgrade a deployment of NetBox v2.10 or earlier, first upgrade to a NetBox v2.11 release, and then upgrade from v2.11 to v3.0. This will avoid any problems with the database migration optimizations implemented in version 3.0. (This is not necessary for new installations.)

As with any other software, if making a major jump (lets say per 2.11 to 3.2), the developers state you should read the release notes for each major (x.x.0) release in between to be sure nothing breaks your integrated scripts and API calls, or the software itself.

I would be happy to put together an FAQ in the wiki for upgrade & install notes, but no one will read it either. I can even link each of the major release notes x.x.0

I agree with you that the information is somewhere, but it is not intuitive. Why make it that hard to find?

You are the first person I have seen mention its hard to find. It seems like you have too much faith in opensource software upgrades by just pushing to prod and not testing. I do not even trust deploying vendor/commercial software or firmware to prod without testing.

@ryanmerolle commented on GitHub (Apr 14, 2022): > I've read the release notes and it's not there: https://netbox.readthedocs.io/en/stable/release-notes/ Its mention in the release notes for 3.0.0. You mentioned you read the release-notes section, but you missed it at the top of the [release-notes for 3.0.0?](https://github.com/netbox-community/netbox/releases/tag/v3.0.0) Here is the blurb: > WARNING: Upgrading an existing NetBox deployment to version 3.0 must be done from version 2.11.0 or later. If attempting to upgrade a deployment of NetBox v2.10 or earlier, first upgrade to a NetBox v2.11 release, and then upgrade from v2.11 to v3.0. This will avoid any problems with the database migration optimizations implemented in version 3.0. (This is not necessary for new installations.) As with any other software, if making a major jump (lets say per 2.11 to 3.2), the developers state you should read the release notes for each major (x.x.0) release in between to be sure nothing breaks your integrated scripts and API calls, or the software itself. I would be happy to put together an FAQ in the wiki for upgrade & install notes, but no one will read it either. I can even link each of the major release notes x.x.0 >I agree with you that the information is somewhere, but it is not intuitive. Why make it that hard to find? You are the first person I have seen mention its hard to find. It seems like you have too much faith in opensource software upgrades by just pushing to prod and not testing. I do not even trust deploying vendor/commercial software or firmware to prod without testing.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
beta
breaking change
complexity: high
complexity: low
complexity: medium
needs milestone
netbox
pending closure
plugin candidate
pull-request
Mirrored from GitHub Pull Request
 severity: high
severity: low
severity: medium
status: accepted
status: backlog
status: blocked
status: duplicate
status: needs owner
status: needs triage
status: revisions needed
status: under review
topic: GraphQL
topic: Internationalization
topic: OpenAPI
topic: UI/UX
topic: cabling
topic: event rules
topic: htmx navigation
topic: industrialization
topic: migrations
topic: plugins
topic: scripts
topic: templating
topic: testing
type: bug
type: deprecation
type: documentation
type: feature
type: housekeeping
type: translation
No Label type: documentation
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
adam
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/netbox#6346
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?