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

/dcim/sites/ Columns Missing After Upgrade from 4.2.6 to 4.3.6. #11483

New Issue
Closed
opened 2025-12-29 21:45:52 +01:00 by adam · 8 comments
adam commented 2025-12-29 21:45:52 +01:00
Owner
Copy Link

Originally created by @pk-lee-developer on GitHub (Aug 14, 2025).

Deployment Type

Self-hosted

NetBox Version

v4.3.6

Python Version

3.12

Steps to Reproduce

  1. Upgrade from v4.2.6 to v4.3.6.
  2. After login, click "Organization", then "Sites".
  3. All sites are missing all columns (null display).
  4. Click on "Configure Table" to add back missing columns.

Expected Behavior

Previous upgrade from older version to v4.2.6 does not exhibit this display issue.

Observed Behavior

Image Image
Originally created by @pk-lee-developer on GitHub (Aug 14, 2025). ### Deployment Type Self-hosted ### NetBox Version v4.3.6 ### Python Version 3.12 ### Steps to Reproduce 1. Upgrade from v4.2.6 to v4.3.6. 2. After login, click "Organization", then "Sites". 3. All sites are missing all columns (null display). 4. Click on "Configure Table" to add back missing columns. ### Expected Behavior Previous upgrade from older version to v4.2.6 does not exhibit this display issue. ### Observed Behavior <img width="1678" height="645" alt="Image" src="https://github.com/user-attachments/assets/2b288590-abeb-4b28-8956-017cfa017652" /> <img width="1668" height="598" alt="Image" src="https://github.com/user-attachments/assets/38519005-88f6-4ec8-bac5-1cfdc8b281d9" />
adam added the type: bug label 2025-12-29 21:45:52 +01:00
adam closed this issue 2025-12-29 21:45:52 +01:00
adam commented 2025-12-29 21:45:53 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Aug 14, 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. Please provide the table configuration you had in place prior to the upgrade.

@jeremystretch commented on GitHub (Aug 14, 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. Please provide the table configuration you had in place prior to the upgrade.
adam commented 2025-12-29 21:45:54 +01:00
Author
Owner
Copy Link

@pk-lee-developer commented on GitHub (Aug 14, 2025):

We roll-back the upgrade. Here is our current v4.2.6 "Sites Display" and my personal "Table Configuration".

Image Image
@pk-lee-developer commented on GitHub (Aug 14, 2025): We roll-back the upgrade. Here is our current v4.2.6 "Sites Display" and my personal "Table Configuration". <img width="1538" height="320" alt="Image" src="https://github.com/user-attachments/assets/675ad7f8-5924-4b3c-9f30-73d0eb9d04c0" /> <img width="1540" height="906" alt="Image" src="https://github.com/user-attachments/assets/d5a8cfcd-53c7-47a8-9ad9-ff89b2e413c4" />
adam commented 2025-12-29 21:45:54 +01:00
Author
Owner
Copy Link

@mr1716 commented on GitHub (Aug 14, 2025):

@pk-lee-developer, what happened if you cleared your personal preferences, did the upgrade, and then reapplied your preferences?

@mr1716 commented on GitHub (Aug 14, 2025): @pk-lee-developer, what happened if you cleared your personal preferences, did the upgrade, and then reapplied your preferences?
adam commented 2025-12-29 21:45:54 +01:00
Author
Owner
Copy Link

@pk-lee-developer commented on GitHub (Aug 14, 2025):

I did this post upgrade and it fixed the sites display issues. The problem is we have hundreds of users and there is no option to bulk clear everyone's sites display's table configuration.

@pk-lee-developer commented on GitHub (Aug 14, 2025): I did this post upgrade and it fixed the sites display issues. The problem is we have hundreds of users and there is no option to bulk clear everyone's sites display's table configuration.
adam commented 2025-12-29 21:45:54 +01:00
Author
Owner
Copy Link

@mr1716 commented on GitHub (Aug 14, 2025):

So the issue is that having preferences will cause the issue, and there’s a way for individuals to fix the issue. But the fix isn’t scalable nor something that admins can do, as even if there were a way to do the reset of the tables, it wouldn’t be very useful friendly nor easy to use. I’m curious that if you were to save the preferences as a saved table configuration, and cleared preferences; would the issue persist?

@mr1716 commented on GitHub (Aug 14, 2025): So the issue is that having preferences will cause the issue, and there’s a way for individuals to fix the issue. But the fix isn’t scalable nor something that admins can do, as even if there were a way to do the reset of the tables, it wouldn’t be very useful friendly nor easy to use. I’m curious that if you were to save the preferences as a saved table configuration, and cleared preferences; would the issue persist?
adam commented 2025-12-29 21:45:55 +01:00
Author
Owner
Copy Link

@pk-lee-developer commented on GitHub (Aug 14, 2025):

if you were to save the preferences as a saved table configuration, and cleared preferences; would the issue persist?

No. It is an one-time issue post upgrade for users until the "Sites" table config is clear.

The only thing I see as a work-around is to write an API call to reset everyone's sites/entire table config to fix this bug.

@pk-lee-developer commented on GitHub (Aug 14, 2025): > if you were to save the preferences as a saved table configuration, and cleared preferences; would the issue persist? No. It is an one-time issue post upgrade for users until the "Sites" table config is clear. The only thing I see as a work-around is to write an API call to reset everyone's sites/entire table config to fix this bug.
adam commented 2025-12-29 21:45:55 +01:00
Author
Owner
Copy Link

@pk-lee-developer commented on GitHub (Aug 15, 2025):

Figure out a work-around via direct DB table update method.

  1. Access NetBox SQL shell.

    $ manage.py dbshell

  2. Reset all users' "data" column to null in "users_userconfig" table.

    netbox=> UPDATE users_userconfig SET data = '{}';

    • This will clear all users' custom preferences to default and fix the "/dcim/sites' display issue.
@pk-lee-developer commented on GitHub (Aug 15, 2025): Figure out a work-around via direct DB table update method. 1. Access NetBox SQL shell. $ manage.py dbshell 2. Reset all users' "data" column to null in "users_userconfig" table. netbox=> UPDATE users_userconfig SET data = '{}'; * This will clear all users' custom preferences to default and fix the "/dcim/sites' display issue.
adam commented 2025-12-29 21:45:56 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Aug 21, 2025):

I'm going to close this out as the issue does not appear to be reproducible (and if it is, we likely don't have a means to backport a fix).

Also FYI user can clear out any saved table configurations under the user preferences view.

@jeremystretch commented on GitHub (Aug 21, 2025): I'm going to close this out as the issue does not appear to be reproducible (and if it is, we likely don't have a means to backport a fix). Also FYI user can clear out any saved table configurations under the user preferences view.
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 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#11483
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?