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

Fragmentation of available IP addresses #6809

New Issue
Closed
opened 2025-12-29 19:45:41 +01:00 by adam · 1 comment
adam commented 2025-12-29 19:45:41 +01:00
Owner
Copy Link

Originally created by @lmelcher1 on GitHub (Aug 15, 2022).

NetBox version

v3.2.8

Python version

3.8

Steps to Reproduce

  1. Click on prefixes
  2. Click on some of them
  3. Click on Ip Adresses tab

image

Expected Behavior

One block between each assigned ip address with count of available

Observed Behavior

image

Available ips are fragmented into blocks

Originally created by @lmelcher1 on GitHub (Aug 15, 2022). ### NetBox version v3.2.8 ### Python version 3.8 ### Steps to Reproduce 1. Click on prefixes 2. Click on some of them 3. Click on Ip Adresses tab ![image](https://user-images.githubusercontent.com/55697949/184607857-4f9d19f6-02a6-45dc-8710-0ebae91380a6.png) ### Expected Behavior One block between each assigned ip address with count of available ### Observed Behavior ![image](https://user-images.githubusercontent.com/55697949/184607904-d99fb79b-6954-4e48-adac-8627e18301af.png) Available ips are fragmented into blocks
adam added the type: bug label 2025-12-29 19:45:41 +01:00
adam closed this issue 2025-12-29 19:45:41 +01:00
adam commented 2025-12-29 19:45:41 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Aug 15, 2022):

  1. Click on prefixes
  2. Click on some of them
  3. Click on Ip Adresses tab

I'm closing this as you have not provided any reproduction steps. If you'd like to invest some time into rewriting this as a valid bug report, you're welcome to do so, and I'll be happy to re-open it once it meets the standards set forth in the bug report template.

@jeremystretch commented on GitHub (Aug 15, 2022): > 1. Click on prefixes > 2. Click on some of them > 3. Click on Ip Adresses tab I'm closing this as you have not provided any reproduction steps. If you'd like to invest some time into rewriting this as a valid bug report, you're welcome to do so, and I'll be happy to re-open it once it meets the standards set forth in the bug report template.
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: 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#6809
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?