-
Notifications
You must be signed in to change notification settings - Fork 2.5k
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
'CircuitTermination' object has no attribute 'name' #5626
Comments
Can you post reliable steps to recreate, starting from creating the object required for this to work (circuit, device, etc) |
Can you be more precise? |
We can only accept bug reports that can be independently reproduced by another party. Per the issue template, please specify the exact steps someone else can take to reproduce the reported behavior on a separate instance of the latest stable release of NetBox. This includes the creation of the necessary circuits and their related objects. |
Folks, I'm getting the exact same issue as well that started after my to 2.10.3. My issue is repeatable and re-producible. This has been working consistently fine from the 2.8.x days of Netbox. In my case I'm doing a URI query against Netbox to gather circuit info into vars via ansible. The call is simple: {{ netbox }}/api/circuits/circuits/?limit=0 TASK [build_vars : Query Netbox circuits api for all circuits.] **************** |
Great. Please detail the steps by which it can be reproduced, as I requested above. Just pointing to a REST API endpoint and pasting the output of an Ansible job isn't enough to reproduce the bug. |
Have you tried at least? |
Hi @jeremystretch, I removed all external components. Steps to reproduce:
$ curl -H "Authorization: Token xxxxxxxxxxxxxxxxxxx" -H "Accept: application/json; indent=4" https://{{ netbox_url}}/api/circuits/circuits/?limit=0 | jq '.'
% Total % Received % Xferd Average Speed Time Time Time Current
Hope this helps! Jim |
I have, and it was not reproducible, hence the request for more information. But you don't have to take my word for it: our CI test for this endpoint also doesn't trigger the bug. So, there's probably something about your specific configuration or data that's causing it. This is why the issue template states:
I'd like to help you, but can't unless you give me more information to work with. |
This isn't a very scientific explanation. But I started trying to narrow down the particular circuit/provider by querying the API based on the provider_id: https://{{netbox_url}}/api/circuits/circuits/?provider_id={{id}} There was one provider with a Termination - Z Side cable connection to a circuit on another provider circuit (A provider1 , B provider2). I deleted the cable id # and low and behold the api error disappeared. Privately @jeremystretch I can share the before and after netbox db sql dumps if you'd like? |
Thank you @Hedius for taking the time to provide a detailed reproduction script per the issue template. Using the information you provided, I was able to replicate the reported bug, and can now work on fixing it. |
Environment
Steps to Reproduce
On the API, in the page 3 i have this error 500:
URL called is : https://netbox/api/circuits/circuits/?cf_technology=VDSL&offset=100&type=s-internet-over-best-effort-line
I have 167 circuits that match my search. Only part 100 - 150 does not work.
This URL works :
URL called is : https://netbox/api/circuits/circuits/?cf_technology=VDSL&type=s-internet-over-best-effort-line
URL called is : https://netbox/api/circuits/circuits/?cf_technology=VDSL&offset=50&type=s-internet-over-best-effort-line
URL called is : https://netbox/api/circuits/circuits/?cf_technology=VDSL&offset=150&type=s-internet-over-best-effort-line
The text was updated successfully, but these errors were encountered: