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

IP Ranges gone after upgrade to 4.0.2 #9727

New Issue
Closed
opened 2025-12-29 21:21:41 +01:00 by adam · 5 comments
adam commented 2025-12-29 21:21:41 +01:00
Owner
Copy Link

Originally created by @peterge-misoft on GitHub (May 23, 2024).

Deployment Type

Self-hosted

NetBox Version

v4.0.2

Python Version

3.10

Steps to Reproduce

We use netbox docker and auto upgrade similar to watchtower.
One of the past upgrades have removed all our IP Ranges which were configured in netbox.
After adding the 172.16.0.1/20 range manually, it does not show available IPs (as it did before the upgrade):
image
image

Expected Behavior

Show the IP ranges like before the upgrade (we had like 20 different IP ranges in our instance).
Show the available IP button when there are IPs available in the range.

Observed Behavior

The IP Ranges page was blank, no range was in there anymore.

I also posted https://github.com/netbox-community/netbox-docker/issues/1244, but they told me to post here.

Originally created by @peterge-misoft on GitHub (May 23, 2024). ### Deployment Type Self-hosted ### NetBox Version v4.0.2 ### Python Version 3.10 ### Steps to Reproduce We use [netbox docker](https://github.com/netbox-community/netbox-docker) and auto upgrade similar to watchtower. One of the past upgrades have removed all our IP Ranges which were configured in netbox. After adding the 172.16.0.1/20 range manually, it does not show available IPs (as it did before the upgrade): ![image](https://github.com/netbox-community/netbox/assets/162673647/ddc925bc-3686-4050-8bbf-4070ccbd23e2) ![image](https://github.com/netbox-community/netbox/assets/162673647/d03c6fea-d300-44ff-b23c-4585e95730a8) ### Expected Behavior Show the IP ranges like before the upgrade (we had like 20 different IP ranges in our instance). Show the available IP button when there are IPs available in the range. ### Observed Behavior The IP Ranges page was blank, no range was in there anymore. I also posted https://github.com/netbox-community/netbox-docker/issues/1244, but they told me to post here.
adam closed this issue 2025-12-29 21:21:41 +01:00
adam commented 2025-12-29 21:21:42 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (May 23, 2024):

Thank you for opening a bug report. Unfortunately, the information you have provided is not sufficient for someone else to attempt to reproduce the reported behavior. Remember, each bug report must include detailed steps that someone else can follow on a clean, empty NetBox installation to reproduce the exact problem you're experiencing. These instructions should include the creation of any involved objects, any configuration changes, and complete accounting of the actions being taken. Also be sure that your report does not reference data on the public NetBox demo, as that is subject to change at any time by an outside party and cannot be relied upon for bug reports.

@jeremystretch commented on GitHub (May 23, 2024): Thank you for opening a bug report. Unfortunately, the information you have provided is not sufficient for someone else to attempt to reproduce the reported behavior. Remember, each bug report must include detailed steps that someone else can follow on a clean, empty NetBox installation to reproduce the exact problem you're experiencing. These instructions should include the creation of any involved objects, any configuration changes, and complete accounting of the actions being taken. Also be sure that your report does not reference data on the public NetBox demo, as that is subject to change at any time by an outside party and cannot be relied upon for bug reports.
adam commented 2025-12-29 21:21:42 +01:00
Author
Owner
Copy Link

@peterge-misoft commented on GitHub (May 23, 2024):

The problem is that I cant provide this data, because the IP Ranges have been configured by another person. I am able to add new ranges, but now the green "X IPs are free" button which redirects directly to the page that adds the first next free IP Adress is gone. How can I get this button back?

@peterge-misoft commented on GitHub (May 23, 2024): The problem is that I cant provide this data, because the IP Ranges have been configured by another person. I am able to add new ranges, but now the green "X IPs are free" button which redirects directly to the page that adds the first next free IP Adress is gone. How can I get this button back?
adam commented 2025-12-29 21:21:42 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (May 23, 2024):

Show the IP ranges like before the upgrade (we had like 20 different IP ranges in our instance).

IP ranges continue to be displayed as they were in v3.7. What specifically are you reporting as a bug? If you don't see any of your ranges that previously existed after upgrading, it's likely an issue with your deployment.

@jeremystretch commented on GitHub (May 23, 2024): > Show the IP ranges like before the upgrade (we had like 20 different IP ranges in our instance). IP ranges continue to be displayed as they were in v3.7. What specifically are you reporting as a bug? If you don't see any of your ranges that previously existed after upgrading, it's likely an issue with your deployment.
adam commented 2025-12-29 21:21:42 +01:00
Author
Owner
Copy Link

@peterge-misoft commented on GitHub (May 23, 2024):

Idk, everything else in our netbox instance is working fine, just the ip ranges are gone

@peterge-misoft commented on GitHub (May 23, 2024): Idk, everything else in our netbox instance is working fine, just the ip ranges are gone
adam commented 2025-12-29 21:21:43 +01:00
Author
Owner
Copy Link

@peterge-misoft commented on GitHub (May 23, 2024):

OMG I mixed up Prefixes with Ranges. Sorry!

@peterge-misoft commented on GitHub (May 23, 2024): OMG I mixed up Prefixes with Ranges. Sorry!
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
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#9727
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?