Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

KeyError: parent when accessing IP Address List #5091

Closed
tscs37 opened this issue Sep 2, 2020 · 1 comment
Closed

KeyError: parent when accessing IP Address List #5091

tscs37 opened this issue Sep 2, 2020 · 1 comment
Assignees
Labels
status: accepted This issue has been accepted for implementation type: bug A confirmed report of unexpected behavior in the application

Comments

@tscs37
Copy link

tscs37 commented Sep 2, 2020

Environment

  • Python version: 3.7.9
  • NetBox version: 2.9.2
  • Docker Image: netboxcommunity/netbox:2.9.2-ldap

Steps to Reproduce

  1. Setup Netbox 2.8.9
  2. Fill in IP Addresses
  3. Set the table to display the "Parent" column or create a user setting like this:
tables.IPAddressDetailTable.columns: ['address', 'vrf', 'status', 'role', 'tenant', 'assigned', 'dns_name', 'description', 'parent']
  1. Upgrade to 2.9.x
  2. The parent column no longer exists, Netbox produces an error and does not indicate this is related to a bad user setting

Expected Behavior

A list of IP Addresses is shown, Netbox either warns the user that their table configuration is now invalid or clears the invalid column from the user settings.

Observed Behavior

Netbox shows an error page:

There was a problem with your request. Please contact an administrator.

The complete exception is provided below:

<class 'KeyError'>

'parent'

Python version: 3.7.9
NetBox version: 2.9.2
If further assistance is required, please post to the NetBox mailing list.

@jeremystretch jeremystretch added status: accepted This issue has been accepted for implementation type: bug A confirmed report of unexpected behavior in the application labels Sep 2, 2020
@jeremystretch jeremystretch self-assigned this Sep 2, 2020
@jeremystretch
Copy link
Member

Workaround: Navigate user profile > preferences and delete the column ordering for the affected table.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Dec 2, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
status: accepted This issue has been accepted for implementation type: bug A confirmed report of unexpected behavior in the application
Projects
None yet
Development

No branches or pull requests

2 participants