Dropdowns for all forms appear empty after upgrade

[ethnt]

Deployment Type

Self-hosted

Triage priority

N/A

NetBox Version

v4.1.3

Python Version

3.12

Steps to Reproduce

1. Beginning on v3.7.8, add data (device roles, for example)
2. Upgrade to v4.1.3
3. Attempt to create a device using the previously created device role

Expected Behavior

The dropdowns should be populated with the corresponding data.

Observed Behavior

Dropdowns are empty, despite having data available.

[arthanson]

@ethnt I think there is something else going wrong here, I just did a test upgrade from v3.7 to v4.1.5 and it works fine (see screenshot). The drop-downs get their data from the REST API so it might possibly be something wrong with that - maybe go to the REST API explorer (link at the bottom of the NetBox UI - the small icons - see second screenshot).

It might be better to close this issue and open it up as a discussion as it will be to the larger community and they might have more suggestions.

[99-lives]

Hello,

I'm experiencing the same issue here, but on a completely fresh Netbox docker install.

• Netbox version: v4.1.6
• netbox-docker version: 3.0.2
• PostgreSQL: v16

I've created a single Site, but when I go to create a Rack, I cannot select my Site from the dropdown. The same is for Site to Tennant, or Site to Region. No dropdowns that relate to other objects are populating. However, when I use the object selector when creating a Rack, it is able to find my Site. But when I select the Site, nothing happens on the web form, and a Javascript error is logged to the console. That error is:

netbox.js?v=4.1.6:20  Uncaught TypeError: Cannot read properties of undefined (reading 'setData')
    at _q (netbox.js?v=4.1.6:20:37103)
    at HTMLAnchorElement.<anonymous> (netbox.js?v=4.1.6:20:37267)
_q @ netbox.js?v=4.1.6:20
(anonymous) @ netbox.js?v=4.1.6:20

• I've checked the Network tab in the browser dev tools, and all requests succeed.
• I can use the REST API Explorer to find my Site, and other objects, without issue.
• The issue is the same in Microsoft Edge, Chrome, and Firefox.

If there's anything more I can do to provide debug information, please let me know.

Cheers.

[99-lives]

Update. Looking at the demo site, I can see that Netbox is making an API call when selecting a dropdown that relates to other objects. It doesn't prepopulate the dropdown on page load.

This API call does not happen on my deployment. Netbox never attempts any API calls to populate the dropdowns. This makes me think it's a Javascript issue somewhere.

[99-lives]

Just fixed it by regenerating static files. It seems that that process wasn't completing properly. Probably worth investigating further, but now that I'm working, I'm happy.