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.

Sign up for GitHub

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

Jump to bottom

Cable path tracing does not work with data imported by nautobot-netbox-importer (KeyError) #260

Closed
glennmatthews opened this issue Apr 8, 2021 · 0 comments · Fixed by #261
Closed

Cable path tracing does not work with data imported by nautobot-netbox-importer (KeyError) #260

glennmatthews opened this issue Apr 8, 2021 · 0 comments · Fixed by #261
Assignees
@glennmatthews
Labels
type: bug Something isn't working as expected
Projects
Release v1.0.0
Milestone
v1.0.0

Comments

@glennmatthews
Copy link
Contributor

Environment

  • Python version: any
  • Nautobot version: 1.0.0b3

Steps to Reproduce

  1. Install Nautobot 1.0.0b3
  2. Install the nautobot-netbox-importer plugin
  3. Import data from NetBox using the importer
  4. In the Nautobot web UI, navigate to the Device detail view for a Device that has connected interfaces, and attempt to access the Interfaces tab.

Expected Behavior

The page should load successfully, including cable traces for any connected interfaces.

Observed Behavior

Nautobot throws a KeyError:

  File "/usr/local/lib/python3.7/site-packages/nautobot/dcim/models/cables.py", line 465, in get_path
    path.append(prefetched[ct_id][object_id])
@glennmatthews glennmatthews added type: bug Something isn't working as expected status: current labels Apr 8, 2021
@glennmatthews glennmatthews added this to the v1.0.0 milestone Apr 8, 2021
@glennmatthews glennmatthews self-assigned this Apr 8, 2021
@glennmatthews glennmatthews added this to To do in Release v1.0.0 via automation Apr 8, 2021
glennmatthews added a commit that referenced this issue Apr 8, 2021
@glennmatthews
Do not coerce provided UUIDs to type-4 but instead accept any type of…
c36a514 
… UUID as potentially valid. Fixes #260
@glennmatthews glennmatthews mentioned this issue Apr 8, 2021
Merged
@jathanism jathanism moved this from To do to In progress in Release v1.0.0 Apr 8, 2021
@paulbukauskas paulbukauskas moved this from In progress to Review in progress in Release v1.0.0 Apr 8, 2021
Release v1.0.0 automation moved this from Review in progress to Done Apr 8, 2021
glennmatthews added a commit that referenced this issue Apr 8, 2021
@glennmatthews
Do not coerce provided UUIDs to type-4 but instead accept any type of…
c96b3d0 
… UUID as potentially valid. Fixes #260 (#261)
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Jul 8, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees

@glennmatthews glennmatthews

Labels
type: bug Something isn't working as expected
Projects
No open projects
Release v1.0.0
  
Done
Milestone
v1.0.0
Development

Successfully merging a pull request may close this issue.

Do not coerce provided UUIDs to version-4 format nautobot/nautobot
1 participant
@glennmatthews