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.

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

ASN Count is not populated in ASN Ranges view #13047

Closed
berahtlv opened this issue Jun 29, 2023 · 0 comments · Fixed by #13053
Closed

ASN Count is not populated in ASN Ranges view #13047

berahtlv opened this issue Jun 29, 2023 · 0 comments · Fixed by #13053
Assignees
Labels
severity: low Does not significantly disrupt application functionality, or a workaround is available status: accepted This issue has been accepted for implementation type: bug A confirmed report of unexpected behavior in the application

Comments

@berahtlv
Copy link

NetBox version

v3.5.4

Python version

3.10

Steps to Reproduce

  1. Create ASN object in 64512-65534 range
  2. Create ASN Range object and define it as the 64512-65534 range
  3. ASN Count is not populated in ASN Ranges view and shows value of 0
  4. In specific ASN Range object view ASN object tab shows ASN numbers included in the range

Same behaviour in the https://demo.netbox.dev instance.

Our instance after some minutes got this error:

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

Cannot resolve keyword 'asn_count' into field. Choices are: created, custom_field_data, description, end, id, journal_entries, last_updated, name, rir, rir_id, slug, start, tagged_items, tags, tenant, tenant_id

Python version: 3.10.6
NetBox version: 3.5.4

Expected Behavior

ASN Count correctly displays number of included ASN objects

Observed Behavior

SHows 0 even though objects can be seen in the specific ASN Range view

@berahtlv berahtlv added the type: bug A confirmed report of unexpected behavior in the application label Jun 29, 2023
@abhi1693 abhi1693 self-assigned this Jun 29, 2023
@abhi1693 abhi1693 added the status: accepted This issue has been accepted for implementation label Jun 29, 2023
abhi1693 added a commit that referenced this issue Jun 29, 2023
@abhi1693 abhi1693 added the severity: low Does not significantly disrupt application functionality, or a workaround is available label Jun 29, 2023
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Oct 5, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
severity: low Does not significantly disrupt application functionality, or a workaround is available status: accepted This issue has been accepted for implementation type: bug A confirmed report of unexpected behavior in the application
Projects
None yet
2 participants