Contact tab backend error #11202

Closed
opened 2025-12-29 21:41:52 +01:00 by adam · 7 comments
Owner

Originally created by @boxstep on GitHub (May 20, 2025).

Deployment Type

Self-hosted

NetBox Version

v4.3.1

Python Version

3.11

Steps to Reproduce

Updated netbox to newest v4.3.1
Performed DB migrations
Restart services
Trying to access "contacts" tab on virtual machines gives following error

Image

Expected Behavior

Contacts tab opened

Observed Behavior

Backend error

[20/May/2025:06:54:07 +0000] "GET /virtualization/virtual-machines/773/contacts/ HTTP/1.1" 500 1583 "https://netbox/virtualization/virtual-machines/773/" "Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:138.0) Gecko/20100101 Firefox/138.0"
::ffff:10.250.16.7 - - [20/May/2025:06:54:07 +0000] "GET /favicon.ico HTTP/1.1" 404 8278 "https://netbox/virtualization/virtual-machines/773/contacts/" "Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:138.0) Gecko/20100101 Firefox/138.0"

Originally created by @boxstep on GitHub (May 20, 2025). ### Deployment Type Self-hosted ### NetBox Version v4.3.1 ### Python Version 3.11 ### Steps to Reproduce Updated netbox to newest v4.3.1 Performed DB migrations Restart services Trying to access "contacts" tab on virtual machines gives following error ![Image](https://github.com/user-attachments/assets/0558753e-f4b7-4276-8bab-b6fe60d056dd) ### Expected Behavior Contacts tab opened ### Observed Behavior Backend error [20/May/2025:06:54:07 +0000] "GET /virtualization/virtual-machines/773/contacts/ HTTP/1.1" 500 1583 "https://netbox/virtualization/virtual-machines/773/" "Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:138.0) Gecko/20100101 Firefox/138.0" ::ffff:10.250.16.7 - - [20/May/2025:06:54:07 +0000] "GET /favicon.ico HTTP/1.1" 404 8278 "https://netbox/virtualization/virtual-machines/773/contacts/" "Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:138.0) Gecko/20100101 Firefox/138.0"
adam added the type: bug label 2025-12-29 21:41:52 +01:00
adam closed this issue 2025-12-29 21:41:52 +01:00
Author
Owner

@bctiemann commented on GitHub (May 22, 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.

@bctiemann commented on GitHub (May 22, 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

@boxstep commented on GitHub (May 22, 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.

What more information would you need to try to reproduce the bug? No plugins are installed. I did upgrade from 4.1.6 --> 4.3.1 can that be the issue skipping more versions on the database?

@boxstep commented on GitHub (May 22, 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. What more information would you need to try to reproduce the bug? No plugins are installed. I did upgrade from 4.1.6 --> 4.3.1 can that be the issue skipping more versions on the database?
Author
Owner

@bctiemann commented on GitHub (May 22, 2025):

I'm not able to reproduce it using the demo data at https://github.com/netbox-community/netbox-demo-data/tree/master/sql . Do you see the issue using that data, or does it depend on there being some specific data already present during the upgrade? What contact data do you have in the devices that cause the error? Do different devices' detail pages succeed and others fail?

@bctiemann commented on GitHub (May 22, 2025): I'm not able to reproduce it using the demo data at https://github.com/netbox-community/netbox-demo-data/tree/master/sql . Do you see the issue using that data, or does it depend on there being some specific data already present during the upgrade? What contact data do you have in the devices that cause the error? Do different devices' detail pages succeed and others fail?
Author
Owner

@boxstep commented on GitHub (May 22, 2025):

I'm gonna test with demo data later and let you know.

This does happen either on DCIM devices and Virtual machines. We use contact groups inside virtual machine(or device) contacts tab, which open correctly from: Organization -> Contact groups.

What i also witnessed that superuser is able to open Virtual machine contacts tab without issues. My user has full permissions on everything but i get backend error instead of some permissions error.

@boxstep commented on GitHub (May 22, 2025): I'm gonna test with demo data later and let you know. This does happen either on DCIM devices and Virtual machines. We use contact groups inside virtual machine(or device) contacts tab, which open correctly from: Organization -> Contact groups. What i also witnessed that superuser is able to open Virtual machine contacts tab without issues. My user has full permissions on everything but i get backend error instead of some permissions error.
Author
Owner

@bctiemann commented on GitHub (May 22, 2025):

It would also be great if you could find the complete traceback in the server logs; the partial one shown in the screenshot doesn't provide many clues as to where the issue might be.

@bctiemann commented on GitHub (May 22, 2025): It would also be great if you could find the complete traceback in the server logs; the partial one shown in the screenshot doesn't provide many clues as to where the issue might be.
Author
Owner

@boxstep commented on GitHub (May 22, 2025):

@bctiemann Issue resolved. It appears only my user was affected which had same permissions as other users. I deleted my user, recreated with same permissions and now i am able to open contacts tab on DCIM,Virtual Machines. Very strange error.

We can close this if you don't want to dig deeper, but viewing the logs i did not see anything more than what i submitted in this issue. Only error 500 and 404.

@boxstep commented on GitHub (May 22, 2025): @bctiemann Issue resolved. It appears only my user was affected which had same permissions as other users. I deleted my user, recreated with same permissions and now i am able to open contacts tab on DCIM,Virtual Machines. Very strange error. We can close this if you don't want to dig deeper, but viewing the logs i did not see anything more than what i submitted in this issue. Only error 500 and 404.
Author
Owner

@bctiemann commented on GitHub (May 22, 2025):

Thanks, glad you were able to resolve it. It's likely there is some corner case in upgrading stale/incompatible data and it's good to know there's a workaround, but it probably isn't worth the time to try to chase it down proactively.

@bctiemann commented on GitHub (May 22, 2025): Thanks, glad you were able to resolve it. It's likely there is some corner case in upgrading stale/incompatible data and it's good to know there's a workaround, but it probably isn't worth the time to try to chase it down proactively.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/netbox#11202