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

Changing an IP range over reserved IP addresses is not blocked #11272

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

Originally created by @okoeroo on GitHub (Jun 7, 2025).

Deployment Type

Self-hosted

NetBox Version

v4.3.2

Python Version

3.10

Steps to Reproduce

  1. Create IP addresses. Assign them or reserve them. Make a list of them up to .50
  2. Create an IP range. Observer overlap blocking, when .50 is included in the range. And let it start from .51 to 100.
  3. Change range from .51 to overlap over .50 and below. Observe no obstruction to the change.

Expected Behavior

Expected was a similar block to avoid a change of a range over an already existing IP address, regardless of status.

Observed Behavior

The observed behavior is:

  1. No block to make the range change.
  2. Range change is committed in the database without error.
Originally created by @okoeroo on GitHub (Jun 7, 2025). ### Deployment Type Self-hosted ### NetBox Version v4.3.2 ### Python Version 3.10 ### Steps to Reproduce 1. Create IP addresses. Assign them or reserve them. Make a list of them up to .50 2. Create an IP range. Observer overlap blocking, when .50 is included in the range. And let it start from .51 to 100. 3. Change range from .51 to overlap over .50 and below. Observe no obstruction to the change. ### Expected Behavior Expected was a similar block to avoid a change of a range over an already existing IP address, regardless of status. ### Observed Behavior The observed behavior is: 1. No block to make the range change. 2. Range change is committed in the database without error.
adam added the type: bugpending closurestatus: revisions needed labels 2025-12-29 21:42:44 +01:00
adam closed this issue 2025-12-29 21:42:45 +01:00
adam commented 2025-12-29 21:42:45 +01:00
Author
Owner
Copy Link

@jnovinger commented on GitHub (Jun 9, 2025):

Thank you for opening a bug report, @okoeroo . 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.

@jnovinger commented on GitHub (Jun 9, 2025): Thank you for opening a bug report, @okoeroo . 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:42:45 +01:00
Author
Owner
Copy Link

@github-actions[bot] commented on GitHub (Jun 17, 2025):

This is a reminder that additional information is needed in order to further triage this issue. If the requested details are not provided, the issue will soon be closed automatically.

@github-actions[bot] commented on GitHub (Jun 17, 2025): This is a reminder that additional information is needed in order to further triage this issue. If the requested details are not provided, the issue will soon be closed automatically.
adam commented 2025-12-29 21:42:45 +01:00
Author
Owner
Copy Link

@github-actions[bot] commented on GitHub (Jun 24, 2025):

This issue is being closed as no further information has been provided. If you would like to revisit this topic, please first modify your original post to include all the requested detail, and then ask that the issue be reopened.

@github-actions[bot] commented on GitHub (Jun 24, 2025): This issue is being closed as no further information has been provided. If you would like to revisit this topic, please first modify your original post to include all the requested detail, and then ask that the issue be reopened.
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 pending closure status: revisions needed type: bug
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#11272
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?