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

IPAM migration 0072 not performant with large number of existing prefixes #10672

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

Originally created by @jeremystretch on GitHub (Jan 20, 2025).

Originally assigned to: @jeremystretch on GitHub.

Deployment Type

NetBox Cloud

NetBox Version

v4.2.2

Python Version

3.10

Steps to Reproduce

  1. Create a large number of prefixes (e.g. 20,000) in a previous NetBox release.
  2. Upgrade to NetBox v4.2.0 or later.

Expected Behavior

The database migrations should complete within a reasonable amount of time.

Observed Behavior

The 0072_prefix_cached_relations migration within the ipam app can take an excessively long time to complete when there exist many thousands of prefixes in the database. This is due to a missing batch_size parameter in the bulk_update() operation.

Originally created by @jeremystretch on GitHub (Jan 20, 2025). Originally assigned to: @jeremystretch on GitHub. ### Deployment Type NetBox Cloud ### NetBox Version v4.2.2 ### Python Version 3.10 ### Steps to Reproduce 1. Create a large number of prefixes (e.g. 20,000) in a previous NetBox release. 2. Upgrade to NetBox v4.2.0 or later. ### Expected Behavior The database migrations should complete within a reasonable amount of time. ### Observed Behavior The [`0072_prefix_cached_relations`](https://github.com/netbox-community/netbox/blob/main/netbox/ipam/migrations/0072_prefix_cached_relations.py) migration within the `ipam` app can take an excessively long time to complete when there exist many thousands of prefixes in the database. This is due to a missing `batch_size` parameter in the `bulk_update()` operation.
adam added the type: bugstatus: acceptedseverity: medium labels 2025-12-29 21:34:34 +01:00
adam closed this issue 2025-12-29 21:34:34 +01:00
adam commented 2025-12-29 21:34:35 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Jan 20, 2025):

I've found a similar issue with two other v4.2 migrations affecting clusters and circuit terminations.

@jeremystretch commented on GitHub (Jan 20, 2025): I've found a similar issue with two other v4.2 migrations affecting clusters and circuit terminations.
adam commented 2025-12-29 21:34:35 +01:00
Author
Owner
Copy Link

@tyler-8 commented on GitHub (Jan 21, 2025):

Glad to see this as my environment has 50K+ prefixes and 12K+ circuits w/terminations.

@tyler-8 commented on GitHub (Jan 21, 2025): Glad to see this as my environment has 50K+ prefixes and 12K+ circuits w/terminations.
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 severity: medium status: accepted 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#10672
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?