IP Address Bulk Import unable to update. #8335

Closed
opened 2025-12-29 20:35:29 +01:00 by adam · 2 comments
Owner

Originally created by @tamatsuna on GitHub (Jul 14, 2023).

NetBox version

v3.5.6

Python version

3.8

Steps to Reproduce

  1. Open "IP Address Bulk Import".
  2. Fill in the required information, including the value of the id.
  3. Click "Submit" button.

Expected Behavior

Information on existing IP addresses can be updated.

Observed Behavior

Error occered

<class 'ValueError'>

'IPAddressImportForm' has no field named 'assigned_object_id'.

Python version: 3.8.11
NetBox version: 3.5.6
Originally created by @tamatsuna on GitHub (Jul 14, 2023). ### NetBox version v3.5.6 ### Python version 3.8 ### Steps to Reproduce 1. Open "IP Address Bulk Import". 2. Fill in the required information, including the value of the id. 3. Click "Submit" button. ### Expected Behavior Information on existing IP addresses can be updated. ### Observed Behavior Error occered ``` <class 'ValueError'> 'IPAddressImportForm' has no field named 'assigned_object_id'. Python version: 3.8.11 NetBox version: 3.5.6 ```
adam added the type: bug label 2025-12-29 20:35:29 +01:00
adam closed this issue 2025-12-29 20:35:29 +01:00
Author
Owner

@jeremystretch commented on GitHub (Jul 14, 2023):

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 (Jul 14, 2023): 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.
Author
Owner

@tamatsuna commented on GitHub (Jul 18, 2023):

My apologies. The error was caused by the fact that "assigned_object_type" was set to "dcim.interface".
I don't know why this value is in there, but I fixed it by manually updating the target IP address.
Thank you very much.

"role": null,
"assigned_object_type": "dcim.interface",
"assigned_object_id": null,
"assigned_object": null,
@tamatsuna commented on GitHub (Jul 18, 2023): My apologies. The error was caused by the fact that "assigned_object_type" was set to "dcim.interface". I don't know why this value is in there, but I fixed it by manually updating the target IP address. Thank you very much. ``` "role": null, "assigned_object_type": "dcim.interface", "assigned_object_id": null, "assigned_object": null, ```
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/netbox#8335