question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Toggling cable from installed, to planned back to installed breaks cable tracing.

See original GitHub issue

Environment

  • Python version: 3.9.1
  • NetBox version: 2.10.1

After I connect an interface to another interface or rear port (have only tested these two), then toggle the cable from installed, to planned and back to installed, cable tracing breaks with the following error.

<class 'dcim.models.cables.CablePath.DoesNotExist'>

CablePath matching query does not exist.

Python version: 3.9.1
NetBox version: 2.10.1

Steps to Reproduce

  1. Connect cable to another interface or rear port. Cable tracking works.
  2. Mark cable as planned. Cable tracking works and shows cable as planned.
  3. Mark cable as installed. Cable tracing breaks with the error shown above.

Expected Behavior

Expect that toggling the cable between planned and installed doesn’t break tracing.

Observed Behavior

Toggling the cable from installed, to planned back to installed breaks cable tracing.

A side note, I think the icon for a connected and planned cable should be swapped.

Connected cable icon.

Screen Shot 2020-12-17 at 12 48 46 PM

Planned cable icon.

Screen Shot 2020-12-17 at 12 49 00 PM

Issue Analytics

  • State:closed
  • Created 3 years ago
  • Reactions:1
  • Comments:6 (3 by maintainers)

github_iconTop GitHub Comments

1reaction
jchristopher327commented, Dec 21, 2020

I cannot reproduce the problem after setting CACHE_TIMEOUT = 0.

0reactions
jeremystretchcommented, Dec 21, 2020

Ah, I see. This seems to be a caching bug. Just to confirm, if you disable caching by setting CACHE_TIMEOUT = 0 in configuration.py, can you still reproduce the problem?

Read more comments on GitHub >

github_iconTop Results From Across the Web

Cable Tracing – Up to 600 V? - Fluke Networks
Connecting the Transmitter, technicians using the Receiver can easily trace an individual cable, find shorts and breaks, or locate connections ...
Read more >
for use with 3M™ Dynatel™ Cable and Pipe Locators
permanently installed transmitters at strategic locations for use in tracing the cable. If they can transmit 577 Hz, 512 Hz or 560 Hz,...
Read more >
CABLE TRACKER - Harbor Freight Tools
The Cable Tracker is designed to safely identify and trace ires or cable. ithout damaging the insulation, and to check cable circuits...
Read more >
Power Cable Splicing and Terminating Guide
If a cold shrink or premolded splice is being installed, the appropriate splice components must be slid onto the cable(s) before the connection...
Read more >
Tracing out Live Network Cables - YouTube
This clever trick helps you identify un-marked network outlets. A Toner and Tone-probel will not work when a network jack is connected to...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found