An exception when attempting to view IP addresses filtered by a specific VRF. #11393

Closed
opened 2025-12-29 21:44:34 +01:00 by adam · 10 comments
Owner

Originally created by @someconservator on GitHub (Jul 18, 2025).

Deployment Type

Self-hosted

NetBox Version

v4.3.3

Python Version

3.12

Steps to Reproduce

  1. go https://netbox.fqdn/ipam/ip-addresses/
  2. Filters -> Assigned VRF -> choose specified (one!) VRF
  3. Search

Expected Behavior

List of IPs

Observed Behavior

https://netbox.fqdn/ipam/ip-addresses/?vrf_id=39

Server Error

There was a problem with your request. Please contact an administrator.

The complete exception is provided below:

<class 'AttributeError'>

'NoneType' object has no attribute 'get_absolute_url'

Python version: 3.11.11
NetBox version: 4.3.3
Plugins: None installed

Originally created by @someconservator on GitHub (Jul 18, 2025). ### Deployment Type Self-hosted ### NetBox Version v4.3.3 ### Python Version 3.12 ### Steps to Reproduce 1. go https://netbox.fqdn/ipam/ip-addresses/ 2. Filters -> Assigned VRF -> choose specified (one!) VRF 3. Search ### Expected Behavior List of IPs ### Observed Behavior https://netbox.fqdn/ipam/ip-addresses/?vrf_id=39 Server Error There was a problem with your request. Please contact an administrator. The complete exception is provided below: <class 'AttributeError'> 'NoneType' object has no attribute 'get_absolute_url' Python version: 3.11.11 NetBox version: 4.3.3 Plugins: None installed
adam added the type: bugpending closurestatus: revisions needed labels 2025-12-29 21:44:34 +01:00
adam closed this issue 2025-12-29 21:44:34 +01:00
Author
Owner

@jeremystretch commented on GitHub (Jul 18, 2025):

Thank you for opening a bug report. Unfortunately, the information you have provided is not sufficient for someone else to attempt to reproduce the reported behavior. Remember, each bug report must include detailed steps that someone else can follow on a clean, empty NetBox installation to reproduce the exact problem you're experiencing. These instructions should include the creation of any involved objects, any configuration changes, and complete accounting of the actions being taken. Also be sure that your report does not reference data on the public NetBox demo, as that is subject to change at any time by an outside party and cannot be relied upon for bug reports.

@jeremystretch commented on GitHub (Jul 18, 2025): Thank you for opening a bug report. Unfortunately, the information you have provided is not sufficient for someone else to attempt to reproduce the reported behavior. Remember, each bug report must include detailed steps that someone else can follow on a clean, empty NetBox installation to reproduce the exact problem you're experiencing. These instructions should include the creation of any involved objects, any configuration changes, and complete accounting of the actions being taken. Also be sure that your report does not reference data on the public NetBox demo, as that is subject to change at any time by an outside party and cannot be relied upon for bug reports.
Author
Owner

@someconservator commented on GitHub (Jul 19, 2025):

Jeremy,
may i ask what additional data would be nice to provide here to clarify what is happening in more detail?
Thank you.

@someconservator commented on GitHub (Jul 19, 2025): Jeremy, may i ask what additional data would be nice to provide here to clarify what is happening in more detail? Thank you.
Author
Owner

@stuntguy3000 commented on GitHub (Jul 21, 2025):

@someconservator I've been unable to replicate this issue.

In this example,

  • I've created 2x VRFs
  • I've created 2x IP Addresses (one assigned to each VRF)
  • I've successfully filtered by a VRF
Image Image Image

Jeremy is referring to the specific steps of how this issue can be reproduced - is this something you can provide us with?

@stuntguy3000 commented on GitHub (Jul 21, 2025): @someconservator I've been unable to replicate this issue. In this example, - I've created 2x VRFs - I've created 2x IP Addresses (one assigned to each VRF) - I've successfully filtered by a VRF <img width="1920" height="937" alt="Image" src="https://github.com/user-attachments/assets/9384d758-fc07-4add-9bf0-c75e7cfe44ee" /> <img width="1920" height="937" alt="Image" src="https://github.com/user-attachments/assets/05f87d40-190c-465a-ab42-e6b9a2c4f66d" /> <img width="1920" height="937" alt="Image" src="https://github.com/user-attachments/assets/2dda58ec-e96d-47b8-b1ed-dda291b2b254" /> Jeremy is referring to the **specific** steps of how this issue can be reproduced - is this something you can provide us with?
Author
Owner

@someconservator commented on GitHub (Jul 24, 2025):

May be this? 511 IP-addresses in 34 prefixes?
Image

@someconservator commented on GitHub (Jul 24, 2025): May be this? 511 IP-addresses in 34 prefixes? <img width="796" height="131" alt="Image" src="https://github.com/user-attachments/assets/f3e927b8-48c7-4309-9267-d17f41fa1713" />
Author
Owner

@stuntguy3000 commented on GitHub (Jul 24, 2025):

May be this? 511 IP-addresses in 34 prefixes?
Image

Are you able to share this data?

@stuntguy3000 commented on GitHub (Jul 24, 2025): > May be this? 511 IP-addresses in 34 prefixes? > <img width="796" height="131" alt="Image" src="https://github.com/user-attachments/assets/f3e927b8-48c7-4309-9267-d17f41fa1713" /> Are you able to share this data?
Author
Owner

@someconservator commented on GitHub (Jul 24, 2025):

I guess I need to ask our security department about this and they will most likely ask me to specify what exactly needs to be shared. Could you help me specify which specific tables or parts of ones need to be shared? Or all IPAM?

@someconservator commented on GitHub (Jul 24, 2025): I guess I need to ask our security department about this and they will most likely ask me to specify what exactly needs to be shared. Could you help me specify which specific tables or parts of ones need to be shared? Or all IPAM?
Author
Owner

@stuntguy3000 commented on GitHub (Jul 24, 2025):

I guess I need to ask our security department about this and they will most likely ask me to specify what exactly needs to be shared. Could you help me specify which specific tables or parts of ones need to be shared? Or all IPAM?

The minimum viable data to reproduce the issue would be required here, even if you fudge some of the numbers. It would be useful to see if you can replicate the problem.

@stuntguy3000 commented on GitHub (Jul 24, 2025): > I guess I need to ask our security department about this and they will most likely ask me to specify what exactly needs to be shared. Could you help me specify which specific tables or parts of ones need to be shared? Or all IPAM? The minimum viable data to reproduce the issue would be required here, even if you fudge some of the numbers. It would be useful to see if you can replicate the problem.
Author
Owner

@someconservator commented on GitHub (Jul 30, 2025):

In short, it looks like it's again a lack of time to execute a query for large samples. I increased the wait time for the gunicorn to 3 minutes and the bug went away. We probably just have a large database.

@someconservator commented on GitHub (Jul 30, 2025): In short, it looks like it's again a lack of time to execute a query for large samples. I increased the wait time for the gunicorn to 3 minutes and the bug went away. We probably just have a large database.
Author
Owner

@github-actions[bot] commented on GitHub (Aug 7, 2025):

This is a reminder that additional information is needed in order to further triage this issue. If the requested details are not provided, the issue will soon be closed automatically.

@github-actions[bot] commented on GitHub (Aug 7, 2025): This is a reminder that additional information is needed in order to further triage this issue. If the requested details are not provided, the issue will soon be closed automatically.
Author
Owner

@github-actions[bot] commented on GitHub (Aug 15, 2025):

This issue is being closed as no further information has been provided. If you would like to revisit this topic, please first modify your original post to include all the requested detail, and then ask that the issue be reopened.

@github-actions[bot] commented on GitHub (Aug 15, 2025): This issue is being closed as no further information has been provided. If you would like to revisit this topic, please first modify your original post to include all the requested detail, and then ask that the issue be reopened.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/netbox#11393