Assigned column in IP Addresses view is referencing a field that does not exist #4200

Closed
opened 2025-12-29 18:33:49 +01:00 by adam · 1 comment
Owner

Originally created by @brandomando on GitHub (Oct 19, 2020).

Environment

  • Python version: 3.7.9
  • NetBox version: 2.9.2

Steps to Reproduce

  1. Assign an IP address to a device/interface
  2. Look in IPAM IP Addresses - Assigned column is empty
  3. Click to sort by assigned - Django error occurs
<class 'django.core.exceptions.FieldError'>

Cannot resolve keyword 'assigned' into field. Choices are: address, assigned_object, assigned_object_id, assigned_object_type, assigned_object_type_id, created, custom_field_values, description, dns_name, id, interface, last_updated, nat_inside, nat_inside_id, nat_outside, primary_ip4_for, primary_ip6_for, role, services, status, tagged_items, tags, tenant, tenant_id, vminterface, vrf, vrf_id

Python version: 3.7.9
NetBox version: 2.9.2

Expected Behavior

Assigned object should display in the IP Addresses view under the Assigned column.

Observed Behavior

No assigned object appears in the view. It appears that assigned is not a field in the database, based on the django error that I am seeing.

Originally created by @brandomando on GitHub (Oct 19, 2020). <!-- NOTE: IF YOUR ISSUE DOES NOT FOLLOW THIS TEMPLATE, IT WILL BE CLOSED. This form is only for reproducible bugs. If you need assistance with NetBox installation, or if you have a general question, DO NOT open an issue. Instead, post to our mailing list: https://groups.google.com/g/netbox-discuss Please describe the environment in which you are running NetBox. Be sure that you are running an unmodified instance of the latest stable release before submitting a bug report, and that any plugins have been disabled. --> ### Environment * Python version: 3.7.9 * NetBox version: 2.9.2 <!-- Describe in detail the exact steps that someone else can take to reproduce this bug using the current stable release of NetBox. Begin with the creation of any necessary database objects and call out every operation being performed explicitly. If reporting a bug in the REST API, be sure to reconstruct the raw HTTP request(s) being made: Don't rely on a client library such as pynetbox. --> ### Steps to Reproduce 1. Assign an IP address to a device/interface 2. Look in IPAM IP Addresses - Assigned column is empty 3. Click to sort by assigned - Django error occurs ``` <class 'django.core.exceptions.FieldError'> Cannot resolve keyword 'assigned' into field. Choices are: address, assigned_object, assigned_object_id, assigned_object_type, assigned_object_type_id, created, custom_field_values, description, dns_name, id, interface, last_updated, nat_inside, nat_inside_id, nat_outside, primary_ip4_for, primary_ip6_for, role, services, status, tagged_items, tags, tenant, tenant_id, vminterface, vrf, vrf_id Python version: 3.7.9 NetBox version: 2.9.2 ``` <!-- What did you expect to happen? --> ### Expected Behavior Assigned object should display in the IP Addresses view under the `Assigned` column. <!-- What happened instead? --> ### Observed Behavior No assigned object appears in the view. It appears that `assigned` is not a field in the database, based on the django error that I am seeing.
adam closed this issue 2025-12-29 18:33:49 +01:00
Author
Owner

@brandomando commented on GitHub (Oct 19, 2020):

I see that this is actually fixed after the version I'm on. I'm going to close this issue.

Thanks,

Brandon

@brandomando commented on GitHub (Oct 19, 2020): I see that this is actually fixed after the version I'm on. I'm going to close this issue. Thanks, Brandon
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/netbox#4200