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

Drop downs not populating after upgrade to 1.9.3 #799

New Issue
Closed
opened 2025-12-29 16:25:57 +01:00 by adam · 2 comments
adam commented 2025-12-29 16:25:57 +01:00
Owner
Copy Link

Originally created by @belzebud on GitHub (Mar 27, 2017).

Issue type: Bug report

Python version:
Python 2.7.9-1
NetBox version:
NetBox 1.9.3

I upgraded from NetBox 1.8.3 to 1.9.3 today. To upgrade I used Option B: Clone the Git Repository.
Everything was working fine before the upgrade, but afterwards I noticed that some drop-down menus are not populating any more.

I added a new rack. I then tried adding a new PDU and linking a PDU socket with a plug on a device but after going to the select tab and choosing the rack (I only have 1 site currently), the device box never populates. The dashes go away but it never shows a list of devices no matter which rack I select (pic attached).

I also tried linking a new switch port to an ethernet port on a network device and I get the same thing. If I go back to racks and devices I entered before the upgrade I see the same behavior where I can't link ports/sockets, so it's not just new additions.

This happens no matter where I start the linking process from; the PDU. device, or switch.

When using the search tab to connect ports/sockets the port box never populates so I can't do it that way either.
netboxdropd

Originally created by @belzebud on GitHub (Mar 27, 2017). Issue type: Bug report **Python version:** Python 2.7.9-1 **NetBox version:** NetBox 1.9.3 I upgraded from NetBox 1.8.3 to 1.9.3 today. To upgrade I used Option B: Clone the Git Repository. Everything was working fine before the upgrade, but afterwards I noticed that some drop-down menus are not populating any more. I added a new rack. I then tried adding a new PDU and linking a PDU socket with a plug on a device but after going to the select tab and choosing the rack (I only have 1 site currently), the device box never populates. The dashes go away but it never shows a list of devices no matter which rack I select (pic attached). I also tried linking a new switch port to an ethernet port on a network device and I get the same thing. If I go back to racks and devices I entered before the upgrade I see the same behavior where I can't link ports/sockets, so it's not just new additions. This happens no matter where I start the linking process from; the PDU. device, or switch. When using the search tab to connect ports/sockets the port box never populates so I can't do it that way either. ![netboxdropd](https://cloud.githubusercontent.com/assets/17045516/24360557/f393a084-1307-11e7-9f1f-3d0f6514b088.png)
adam closed this issue 2025-12-29 16:25:57 +01:00
adam commented 2025-12-29 16:25:58 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Mar 27, 2017):

Did you try forcing a refresh in your browser to pull down the updated Javascript?

@jeremystretch commented on GitHub (Mar 27, 2017): Did you try forcing a refresh in your browser to pull down the updated Javascript?
adam commented 2025-12-29 16:25:58 +01:00
Author
Owner
Copy Link

@belzebud commented on GitHub (Mar 28, 2017):

Sorry, the issue must be with my browser, I've been using Chrome Canary while doing most of the editing. I haven't let it upgrade or restart for over a week, so I didn't think to check a different browser. This morning I tried FireFox and it works there. Something weird happened as a result of the upgrade, but I don't think its the fault of the upgrade. it's probably the browser.

I did try to refresh the browser and clear offline data yesterday, but sometimes when I have weird issues with the Canary build it requires a reinstall.

@belzebud commented on GitHub (Mar 28, 2017): Sorry, the issue must be with my browser, I've been using Chrome Canary while doing most of the editing. I haven't let it upgrade or restart for over a week, so I didn't think to check a different browser. This morning I tried FireFox and it works there. Something weird happened as a result of the upgrade, but I don't think its the fault of the upgrade. it's probably the browser. I did try to refresh the browser and clear offline data yesterday, but sometimes when I have weird issues with the Canary build it requires a reinstall.
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
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#799
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?