starred/netbox
1
0
Fork 0
mirror of https://github.com/netbox-community/netbox.git synced 2026-01-12 05:20:31 +01:00
Code Issues 273 Packages Projects Releases 10 Wiki Activity

Sort on module bay status field error #8610

New Issue
Closed
opened 2025-12-29 20:38:51 +01:00 by adam · 3 comments
adam commented 2025-12-29 20:38:51 +01:00
Owner
Copy Link

Originally created by @ahlee1 on GitHub (Sep 13, 2023).

Originally assigned to: @abhi1693 on GitHub.

NetBox version

v3.6.1

Python version

3.10

Steps to Reproduce

  1. Create a module bay
  2. Sort Module bay on Status
  3. Click on module bay tab again

Expected Behavior

Either:

  1. Sort on Module Bay Status
  2. No sorting on module bay status allowed

Observed Behavior

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

image

Originally created by @ahlee1 on GitHub (Sep 13, 2023). Originally assigned to: @abhi1693 on GitHub. ### NetBox version v3.6.1 ### Python version 3.10 ### Steps to Reproduce 1. Create a module bay 2. Sort Module bay on Status 3. Click on module bay tab again ### Expected Behavior Either: 1. Sort on Module Bay Status 2. No sorting on module bay status allowed ### Observed Behavior `<class 'django.core.exceptions.FieldError'>` ![image](https://github.com/netbox-community/netbox/assets/55637410/3a2f1cc6-abd6-4dea-a7f2-ace3892feadc)
adam added the type: bugstatus: acceptedseverity: low labels 2025-12-29 20:38:51 +01:00
adam closed this issue 2025-12-29 20:38:51 +01:00
adam commented 2025-12-29 20:38:52 +01:00
Author
Owner
Copy Link

@pv2b commented on GitHub (Sep 14, 2023):

This seems to be valid, I can repro this in my own instance. Worse still, the error seems to be persistent, making it impossible to view any more module bays, even after removing browser cookies, implying the corrupted configuration is stored server-side somewhere. I'd say this makes the issue at least "medium" severity because triggering this bug completely disables module bay functionality until a manual fix is made somehow.

@pv2b commented on GitHub (Sep 14, 2023): This seems to be valid, I can repro this in my own instance. Worse still, the error seems to be persistent, making it impossible to view any more module bays, even after removing browser cookies, implying the corrupted configuration is stored server-side somewhere. I'd say this makes the issue at least "medium" severity because triggering this bug completely disables module bay functionality until a manual fix is made somehow.
adam commented 2025-12-29 20:38:52 +01:00
Author
Owner
Copy Link

@abhi1693 commented on GitHub (Sep 14, 2023):

You can clear the table configuration from your profile

@abhi1693 commented on GitHub (Sep 14, 2023): You can clear the table configuration from your profile
adam commented 2025-12-29 20:38:52 +01:00
Author
Owner
Copy Link

@pv2b commented on GitHub (Sep 14, 2023):

You can clear the table configuration from your profile

Thanks for this, I was half-way through trying to figure out how to do it in nbshell, but the workaround if you get stuck in this place is:

  1. Click your username in top right and select Preferences.
  2. Under "Table Configurations" heading, under the "Clear table preferences" section, check the checkbox next to "DeviceModuleBayTable" and press submit.
@pv2b commented on GitHub (Sep 14, 2023): > You can clear the table configuration from your profile Thanks for this, I was half-way through trying to figure out how to do it in nbshell, but the workaround if you get stuck in this place is: 1. Click your username in top right and select Preferences. 2. Under "Table Configurations" heading, under the "Clear table preferences" section, check the checkbox next to "DeviceModuleBayTable" and press submit.
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 severity: low status: accepted type: bug
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#8610
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?