starred/netbox
1
0
Fork 0
mirror of https://github.com/netbox-community/netbox.git synced 2026-01-11 21:10:29 +01:00
Code Issues 273 Packages Projects Releases 10 Wiki Activity

Cannot configure a device on a Circuit Termination point anymore #1346

New Issue
Closed
opened 2025-12-29 16:31:38 +01:00 by adam · 8 comments
adam commented 2025-12-29 16:31:38 +01:00
Owner
Copy Link

Originally created by @jdecorniquet on GitHub (Oct 23, 2017).

Issue type

[ ] Feature request
[X ] Bug report
[ ] Documentation

Environment

  • Python version: 2.7..9
  • NetBox version: 2.2.2

Description

When creating a circuit and editing the termination point, after selecting the site, no device are found/looked up.
More specifically, when I take an existing circuit with termination A-Z already configured, if I change the site (say from site ABC to ZZZ) and then go back to the original, the device do not show up anymore even though it does existing in Netbox.

I upgraded from 2.1.5 to 2.2.2 recently, it used to work before.

Regards,

Originally created by @jdecorniquet on GitHub (Oct 23, 2017). ### Issue type [ ] Feature request [X ] Bug report [ ] Documentation ### Environment * Python version: 2.7..9 * NetBox version: 2.2.2 ### Description When creating a circuit and editing the termination point, after selecting the site, no device are found/looked up. More specifically, when I take an existing circuit with termination A-Z already configured, if I change the site (say from site ABC to ZZZ) and then go back to the original, the device do not show up anymore even though it does existing in Netbox. I upgraded from 2.1.5 to 2.2.2 recently, it used to work before. Regards,
adam closed this issue 2025-12-29 16:31:38 +01:00
adam commented 2025-12-29 16:31:39 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Oct 26, 2017):

Please post the list of steps necessary to recreate the behavior you're describing, beginning with the creation of sites and devices.

@jeremystretch commented on GitHub (Oct 26, 2017): Please post the list of steps necessary to recreate the behavior you're describing, beginning with the creation of sites and devices.
adam commented 2025-12-29 16:31:39 +01:00
Author
Owner
Copy Link

@jdecorniquet commented on GitHub (Oct 27, 2017):

Here is a recent test I did :

  • Create a new tenant "TestTenant"
  • Create a new site "TestSite"
  • Create a new device "TestDevice", assign it to "TestTenant" and
    "TestSite"
  • Create a new circuit "TestCircuit", assign is to "TestTenant"
    • Add to Termination - A Side
    • Select "TestSite"
    • There is no rack
    • Try to select "TestDevice" but it does not show up

Now as I said in the same context, with an already existing circuit where I
did assign everything before 2.2.2, the device is shown in the Termination

  • A Side. If I try to edit the latter to change something, I lose the
    device and can't select it anymore or any other for that matter.

I hope this is enough information else let me know.

Regards,

2017-10-26 9:33 GMT-04:00 Jeremy Stretch notifications@github.com:

Please post the list of steps necessary to recreate the behavior you're
describing, beginning with the creation of sites and devices.

—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/digitalocean/netbox/issues/1637#issuecomment-339667321,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AZpQ6U9nr_WpOhCfgqeaJwAUBvMklkVoks5swIpGgaJpZM4QDDhI
.

--
Jérôme DECORNIQUET

@jdecorniquet commented on GitHub (Oct 27, 2017): Here is a recent test I did : - Create a new tenant "TestTenant" - Create a new site "TestSite" - Create a new device "TestDevice", assign it to "TestTenant" and "TestSite" - Create a new circuit "TestCircuit", assign is to "TestTenant" - Add to Termination - A Side - Select "TestSite" - There is no rack - Try to select "TestDevice" but it does not show up Now as I said in the same context, with an already existing circuit where I did assign everything before 2.2.2, the device is shown in the Termination - A Side. If I try to edit the latter to change something, I lose the device and can't select it anymore or any other for that matter. I hope this is enough information else let me know. Regards, 2017-10-26 9:33 GMT-04:00 Jeremy Stretch <notifications@github.com>: > Please post the list of steps necessary to recreate the behavior you're > describing, beginning with the creation of sites and devices. > > — > You are receiving this because you authored the thread. > Reply to this email directly, view it on GitHub > <https://github.com/digitalocean/netbox/issues/1637#issuecomment-339667321>, > or mute the thread > <https://github.com/notifications/unsubscribe-auth/AZpQ6U9nr_WpOhCfgqeaJwAUBvMklkVoks5swIpGgaJpZM4QDDhI> > . > -- Jérôme DECORNIQUET
adam commented 2025-12-29 16:31:39 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Oct 27, 2017):

When I run through the steps you list, I see TestDevice in the list as expected. Are you sure you didn't assign TestDevice to a rack? (If you did, you'd need to select the rack from the dropdown in the circuit termination form.) Does TestDevice show up in the list at https://netbox/dcim/devices/?rack_id=0?

@jeremystretch commented on GitHub (Oct 27, 2017): When I run through the steps you list, I see TestDevice in the list as expected. Are you sure you didn't assign TestDevice to a rack? (If you did, you'd need to select the rack from the dropdown in the circuit termination form.) Does TestDevice show up in the list at https://netbox/dcim/devices/?rack_id=0?
adam commented 2025-12-29 16:31:40 +01:00
Author
Owner
Copy Link

@jdecorniquet commented on GitHub (Oct 27, 2017):

I did verify and it's not assigned to any rack, nor does it shows at
https://netbox/dcim/devices/?rack_id=0.

Could it be a DB issue after the upgrade ? Everything else is running
smoothly though.

2017-10-27 10:59 GMT-04:00 Jeremy Stretch notifications@github.com:

When I run through the steps you list, I see TestDevice in the list as
expected. Are you sure you didn't assign TestDevice to a rack? (If you did,
you'd need to select the rack from the dropdown in the circuit termination
form.) Does TestDevice show up in the list at
https://netbox/dcim/devices/?rack_id=0?

—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/digitalocean/netbox/issues/1637#issuecomment-339996142,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AZpQ6X8bq_EzfKJ5komeC8aJlkeWvaboks5swe_ZgaJpZM4QDDhI
.

--
Jérôme DECORNIQUET

@jdecorniquet commented on GitHub (Oct 27, 2017): I did verify and it's not assigned to any rack, nor does it shows at https://netbox/dcim/devices/?rack_id=0. Could it be a DB issue after the upgrade ? Everything else is running smoothly though. 2017-10-27 10:59 GMT-04:00 Jeremy Stretch <notifications@github.com>: > When I run through the steps you list, I see TestDevice in the list as > expected. Are you sure you didn't assign TestDevice to a rack? (If you did, > you'd need to select the rack from the dropdown in the circuit termination > form.) Does TestDevice show up in the list at > https://netbox/dcim/devices/?rack_id=0? > > — > You are receiving this because you authored the thread. > Reply to this email directly, view it on GitHub > <https://github.com/digitalocean/netbox/issues/1637#issuecomment-339996142>, > or mute the thread > <https://github.com/notifications/unsubscribe-auth/AZpQ6X8bq_EzfKJ5komeC8aJlkeWvaboks5swe_ZgaJpZM4QDDhI> > . > -- Jérôme DECORNIQUET
adam commented 2025-12-29 16:31:40 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Oct 30, 2017):

Can you post the result you get when querying the API for the device please? (GET https://netbox/api/dcim/devices/<pk>/) If the rack is null the filter should find it.

@jeremystretch commented on GitHub (Oct 30, 2017): Can you post the result you get when querying the API for the device please? (`GET https://netbox/api/dcim/devices/<pk>/`) If the rack is `null` the filter should find it.
adam commented 2025-12-29 16:31:40 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Oct 30, 2017):

It looks like you might have run into #1649. What version of django-filter to you have installed? (You can check with pip freeze | grep django-filter.) If it's 1.1.0 or higher, try downgrading to 1.0.4 for now to see if that fixes the issue (pip install -U django-filter==1.0.4).

@jeremystretch commented on GitHub (Oct 30, 2017): It looks like you might have run into #1649. What version of `django-filter` to you have installed? (You can check with `pip freeze | grep django-filter`.) If it's 1.1.0 or higher, try downgrading to 1.0.4 for now to see if that fixes the issue (`pip install -U django-filter==1.0.4`).
adam commented 2025-12-29 16:31:40 +01:00
Author
Owner
Copy Link

@jdecorniquet commented on GitHub (Oct 31, 2017):

Hello,

First, the GET https://netbox/api/dcim/devices// was indeed showing the null value for the rack.
Last, the django-filter was indeed at version 1.1.0 and downgrading it to 1.0.4 did fix the issue!

Thanks,

@jdecorniquet commented on GitHub (Oct 31, 2017): Hello, First, the GET https://netbox/api/dcim/devices/<pk>/ was indeed showing the null value for the rack. Last, the django-filter was indeed at version 1.1.0 and downgrading it to 1.0.4 did fix the issue! Thanks,
adam commented 2025-12-29 16:31:40 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Oct 31, 2017):

Cool. #1649 will be fixed in v2.2.3. Closing this out.

@jeremystretch commented on GitHub (Oct 31, 2017): Cool. #1649 will be fixed in v2.2.3. Closing this out.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
beta
breaking change
complexity: high
complexity: low
complexity: medium
needs milestone
netbox
pending closure
plugin candidate
pull-request
Mirrored from GitHub Pull Request
 severity: high
severity: low
severity: medium
status: accepted
status: backlog
status: blocked
status: duplicate
status: needs owner
status: needs triage
status: revisions needed
status: under review
topic: GraphQL
topic: Internationalization
topic: OpenAPI
topic: UI/UX
topic: cabling
topic: event rules
topic: htmx navigation
topic: industrialization
topic: migrations
topic: plugins
topic: scripts
topic: templating
topic: testing
type: bug
type: deprecation
type: documentation
type: feature
type: housekeeping
type: translation
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
adam
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/netbox#1346
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?