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

Individual ASN view broken when sorting by circuit count #6478

New Issue
Closed
opened 2025-12-29 19:41:08 +01:00 by adam · 5 comments
adam commented 2025-12-29 19:41:08 +01:00
Owner
Copy Link

Originally created by @DetunizedGravity on GitHub (May 13, 2022).

Originally assigned to: @kkthxbye-code on GitHub.

NetBox version

v3.2.2

Python version

3.8

Steps to Reproduce

  1. Connect to Netbox and authenticated yourself.
  2. Navigate to any kind of view that displays a link to an ASN object, and click on that link

Expected Behavior

Display of the detail page of the selected ASN object.

Observed Behavior

A field error exception was raised:

<class 'django.core.exceptions.FieldError'>

Cannot resolve keyword 'count_circuits' into field. Choices are: account, admin_contact, asn, asns, circuits, comments, contacts, created, custom_field_data, id, journal_entries, last_updated, name, networks, noc_contact, portal_url, slug, tagged_items, tags

Python version: 3.8.10
NetBox version: 3.2.2

Please note that in our context unauthenticated users have a read only rights to most object types and that, strangely, only authenticated users trigger this behaviour.

Originally created by @DetunizedGravity on GitHub (May 13, 2022). Originally assigned to: @kkthxbye-code on GitHub. ### NetBox version v3.2.2 ### Python version 3.8 ### Steps to Reproduce 1. Connect to Netbox and authenticated yourself. 2. Navigate to any kind of view that displays a link to an ASN object, and click on that link ### Expected Behavior Display of the detail page of the selected ASN object. ### Observed Behavior A field error exception was raised: --- <class 'django.core.exceptions.FieldError'> Cannot resolve keyword 'count_circuits' into field. Choices are: account, admin_contact, asn, asns, circuits, comments, contacts, created, custom_field_data, id, journal_entries, last_updated, name, networks, noc_contact, portal_url, slug, tagged_items, tags Python version: 3.8.10 NetBox version: 3.2.2 --- Please note that in our context unauthenticated users have a read only rights to most object types and that, strangely, **only authenticated users trigger this behaviour.**
adam added the type: bugstatus: accepted labels 2025-12-29 19:41:08 +01:00
adam closed this issue 2025-12-29 19:41:09 +01:00
adam commented 2025-12-29 19:41:10 +01:00
Author
Owner
Copy Link

@DetunizedGravity commented on GitHub (May 13, 2022):

Worse than that. Dug deeper. Found that I seem to be the only impacted user. I also happen to be the only user to have worked on ASNs and providers since the upgrade from 3.1.7 to 3.2.2.

@DetunizedGravity commented on GitHub (May 13, 2022): Worse than that. Dug deeper. Found that I seem to be the only impacted user. I also happen to be the only user to have worked on ASNs and providers since the upgrade from 3.1.7 to 3.2.2.
adam commented 2025-12-29 19:41:10 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (May 13, 2022):

Navigate to any kind of view that displays a link to an ASN object, and click on that link

Please say exactly what you're doing.

@jeremystretch commented on GitHub (May 13, 2022): > Navigate to any kind of view that displays a link to an ASN object, and click on that link Please say _exactly_ what you're doing.
adam commented 2025-12-29 19:41:10 +01:00
Author
Owner
Copy Link

@kkthxbye-code commented on GitHub (May 13, 2022):

I managed to replicate this, I think it's a side effect caused by 0301aec409

I'm not at a computer with access to my own netbox instance, so these steps are when importing netbox-demo-data:

Workaround is to clear table preferences for ProviderTable.

@kkthxbye-code commented on GitHub (May 13, 2022): I managed to replicate this, I think it's a side effect caused by https://github.com/netbox-community/netbox/commit/0301aec409fbf29834d3a4cfbecb481a60ec6b8a I'm not at a computer with access to my own netbox instance, so these steps are when importing netbox-demo-data: * Import https://github.com/netbox-community/netbox-demo-data * Go to Circuits -> Providers * Sort table by the "Circuits" column * Go to IPAM -> ASNs * Click any ASN Workaround is to clear table preferences for ProviderTable.
adam commented 2025-12-29 19:41:11 +01:00
Author
Owner
Copy Link

@DetunizedGravity commented on GitHub (May 13, 2022):

Please say exactly what you're doing.

I could have said "Go to IPAM/ASN and click any ASN" but I checked that it also occured when clicking on an ASN link from anywhere some of these appear. I was in a rush and tried to convey that information. Obviously it was not the right way to put it. Next time I'll add it in a comment below instead, to avoid confusion.

About the "sorting provider by circuits count", I did do that, yes. But I had spent so much time working on providers and ASN yesterday and this morning that there was absolutely no way I could have remembered and made the link between this action and the bug. I did see that the issue came from a nested request for provider data when displaying the ASN, but that was about it. My understanding did not go beyond that and I can't try and debug anything in my current work env. I could only have investigated more from home. So... Sorry for the bad quality of the bug report but it was the best I could do at that time.

I do have a doubt about the culprit designated by @kkthxbye-code. Isn't this code change supposed to be present in v3.2.3 and not 3.2.2? I have the issue in 3.2.2, unless my colleagues went for an unannounced upgrade when I was having lunch. And I am 99% certain that I checked the current version when I started having problems.

Edit: typo

@DetunizedGravity commented on GitHub (May 13, 2022): > Please say _exactly_ what you're doing. I could have said "Go to IPAM/ASN and click any ASN" but I checked that it also occured when clicking on an ASN link from anywhere some of these appear. I was in a rush and tried to convey that information. Obviously it was not the right way to put it. Next time I'll add it in a comment below instead, to avoid confusion. About the "sorting provider by circuits count", I did do that, yes. But I had spent so much time working on providers and ASN yesterday and this morning that there was absolutely no way I could have remembered and made the link between this action and the bug. I did see that the issue came from a nested request for provider data when displaying the ASN, but that was about it. My understanding did not go beyond that and I can't try and debug anything in my current work env. I could only have investigated more from home. So... Sorry for the bad quality of the bug report but it was the best I could do at that time. I do have a doubt about the culprit designated by @kkthxbye-code. Isn't this code change supposed to be present in v3.2.3 and not 3.2.2? I have the issue in 3.2.2, unless my colleagues went for an unannounced upgrade when I was having lunch. And I am 99% certain that I checked the current version when I started having problems. Edit: typo
adam commented 2025-12-29 19:41:11 +01:00
Author
Owner
Copy Link

@kkthxbye-code commented on GitHub (May 13, 2022):

I do have a doubt about the culprit designated by @kkthxbye-code. Isn't this code change supposed to be present in v3.2.3 and not 3.2.2? I have the issue in 3.2.2, unless my colleagues went for an unannounced upgrade when I was having lunch. And I am 99% certain that I checked the current version when I started having problems.

My bad, I missed that you were on 3.2.2. It's probably just a missing annotation for the queryset then.

@kkthxbye-code commented on GitHub (May 13, 2022): > I do have a doubt about the culprit designated by @kkthxbye-code. Isn't this code change supposed to be present in v3.2.3 and not 3.2.2? I have the issue in 3.2.2, unless my colleagues went for an unannounced upgrade when I was having lunch. And I am 99% certain that I checked the current version when I started having problems. My bad, I missed that you were on 3.2.2. It's probably just a missing annotation for the queryset then.
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 status: accepted type: bug
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#6478
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?