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

Object (interface) not found when bulk importing IP Addresses #9190

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

Originally created by @thiagomarafeli on GitHub (Feb 2, 2024).

Deployment Type

Self-hosted

NetBox Version

v3.7.1

Python Version

3.10

Steps to Reproduce

  1. Go to Virtualization > Interface and create a new interface
  2. Go to IPAM > IP Addresses and go to the bulk import screen
  3. Try to import a CSV with an IP referencing that interface

Example of import, assuming an interface created in step 1 with the name "eni-123456789", and given the fact that the accessor is name:

address,status,interface
12.123.123.123/32,active,eni-123456789

In this case, I'm trying to associate the IP with an interface attached to a VM and a VRF. Although it's possible to correctly select the interface over UI, on bulk import this is not possible.

Expected Behavior

A successful import

Observed Behavior

An error showed up:
Record 1 interface: Object not found: eni-123456789

Originally created by @thiagomarafeli on GitHub (Feb 2, 2024). ### Deployment Type Self-hosted ### NetBox Version v3.7.1 ### Python Version 3.10 ### Steps to Reproduce 1. Go to Virtualization > Interface and create a new interface 2. Go to IPAM > IP Addresses and go to the bulk import screen 3. Try to import a CSV with an IP referencing that interface Example of import, assuming an interface created in step 1 with the name "eni-123456789", and given the fact that the accessor is `name`: ```csv address,status,interface 12.123.123.123/32,active,eni-123456789 ``` In this case, I'm trying to associate the IP with an interface attached to a VM and a VRF. Although it's possible to correctly select the interface over UI, on bulk import this is not possible. ### Expected Behavior A successful import ### Observed Behavior An error showed up: `Record 1 interface: Object not found: eni-123456789`
adam closed this issue 2025-12-29 20:46:47 +01:00
adam commented 2025-12-29 20:46:48 +01:00
Author
Owner
Copy Link

@thiagomarafeli commented on GitHub (Feb 3, 2024):

I myself realized that it was also necessary to inform in this import the virtual_machine which the interface was associated with.
After that, it worked.

But, I only realized that issue after I tried to set as the primary IP for that interface and an error showed up saying that it was necessary to also inform the device or VM to work. It would be nice if that same message shows when the user try to import the interface without the parent.

Also... isn't missing the FHRP Group in bulk import? I never used FHRP, but if there is the device and virtual_machine fields, shouldn't have a fhrp_group or something like that in bulk import?

I will leave this issue open because of these 2 last comments, but, about the original question, it's not a bug and my issue doesn't exist anymore.

@thiagomarafeli commented on GitHub (Feb 3, 2024): I myself realized that it was also necessary to inform in this import the `virtual_machine` which the interface was associated with. After that, it worked. But, I only realized that issue after I tried to set as the primary IP for that interface and an error showed up saying that it was necessary to also inform the device or VM to work. It would be nice if that same message shows when the user try to import the interface without the parent. Also... isn't missing the FHRP Group in bulk import? I never used FHRP, but if there is the `device` and `virtual_machine` fields, shouldn't have a `fhrp_group` or something like that in bulk import? I will leave this issue open because of these 2 last comments, but, about the original question, it's not a bug and my issue doesn't exist anymore.
adam commented 2025-12-29 20:46:48 +01:00
Author
Owner
Copy Link

@abhi1693 commented on GitHub (Feb 3, 2024):

Since the report in question is working as expected, I'm going to close this issue. Please feel free to open a new FR for your other request.

@abhi1693 commented on GitHub (Feb 3, 2024): Since the report in question is working as expected, I'm going to close this issue. Please feel free to open a new FR for your other request.
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#9190
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?