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

"Current Configuration" of /core/system/ does not take configuration file into account #9885

New Issue
Closed
opened 2025-12-29 21:23:59 +01:00 by adam · 4 comments
adam commented 2025-12-29 21:23:59 +01:00
Owner
Copy Link

Originally created by @mrtn-r on GitHub (Jun 22, 2024).

Originally assigned to: @tobiasge on GitHub.

Deployment Type

Self-hosted

NetBox Version

v4.0.5

Python Version

3.11

Steps to Reproduce

  1. Set up a netbox instance.
  2. Change some value via the configuration.py, e.g. the login banner

Expected Behavior

Expect the changes in the config file to affect the "Current Configuration" part of NETBOXURL/core/system/

Observed Behavior

Changes are not displayed and the default values are used.
However when creating a new config revision and changing exactly nothing, the config file is parsed

Originally created by @mrtn-r on GitHub (Jun 22, 2024). Originally assigned to: @tobiasge on GitHub. ### Deployment Type Self-hosted ### NetBox Version v4.0.5 ### Python Version 3.11 ### Steps to Reproduce 1. Set up a netbox instance. 2. Change some value via the configuration.py, e.g. the login banner ### Expected Behavior Expect the changes in the config file to affect the "Current Configuration" part of NETBOXURL/core/system/ ### Observed Behavior Changes are not displayed and the default values are used. However when creating a new config revision and changing exactly nothing, the config file is parsed
adam added the type: bugstatus: acceptedseverity: medium labels 2025-12-29 21:23:59 +01:00
adam closed this issue 2025-12-29 21:23:59 +01:00
adam commented 2025-12-29 21:24:00 +01:00
Author
Owner
Copy Link

@mrtn-r commented on GitHub (Jun 22, 2024):

Here's a video because maybe my wording isn't clear enough:

https://github.com/netbox-community/netbox/assets/153684711/c054ee03-b413-4b5a-a009-8f16689e2e75

@mrtn-r commented on GitHub (Jun 22, 2024): Here's a video because maybe my wording isn't clear enough: https://github.com/netbox-community/netbox/assets/153684711/c054ee03-b413-4b5a-a009-8f16689e2e75
adam commented 2025-12-29 21:24:00 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Jun 24, 2024):

Thank you for opening a bug report. I was unable to reproduce the reported behavior on NetBox v4.0.5. Please re-confirm the reported behavior on the current stable release and adjust your post above as necessary. Remember to provide detailed steps that someone else can follow using a clean installation of NetBox to reproduce the issue. Remember to include the steps taken to create any initial objects or other data.

@jeremystretch commented on GitHub (Jun 24, 2024): Thank you for opening a bug report. I was unable to reproduce the reported behavior on NetBox v4.0.5. Please re-confirm the reported behavior on the current stable release and adjust your post above as necessary. Remember to provide detailed steps that someone else can follow using a clean installation of NetBox to reproduce the issue. Remember to include the steps taken to create any initial objects or other data.
adam commented 2025-12-29 21:24:00 +01:00
Author
Owner
Copy Link

@azuercher commented on GitHub (Jun 25, 2024):

Hello,
I think I may be seeing similar issue on 4.0.5. I upgraded from 3.7.1. I noticed that netbox is not using my local timezone so I was investigating the issue and it lead me to this report.

I checked configuration.py and it has the timezone set same as previous version (configuration.py was copied during upgrade). If I look at Admin > System is shows my system time is correct:
image

However when updating or editing an object the time displayed is UTC:

image

Additionally, I noticed my configuration.py has
PREFER_IPV4 = True

but in the Admin > System is shows off.
image

Thanks

@azuercher commented on GitHub (Jun 25, 2024): Hello, I think I may be seeing similar issue on 4.0.5. I upgraded from 3.7.1. I noticed that netbox is not using my local timezone so I was investigating the issue and it lead me to this report. I checked configuration.py and it has the timezone set same as previous version (configuration.py was copied during upgrade). If I look at Admin > System is shows my system time is correct: ![image](https://github.com/netbox-community/netbox/assets/1099965/a7c1ae77-f0bc-4a2a-bdcb-29e39fe21613) However when updating or editing an object the time displayed is UTC: ![image](https://github.com/netbox-community/netbox/assets/1099965/7f8ab09f-a156-49ec-b400-28f44d06ae8c) Additionally, I noticed my configuration.py has PREFER_IPV4 = True but in the Admin > System is shows off. ![image](https://github.com/netbox-community/netbox/assets/1099965/c5da0c11-3190-4594-b864-8330aa87c52b) Thanks
adam commented 2025-12-29 21:24:01 +01:00
Author
Owner
Copy Link

@tobiasge commented on GitHub (Jun 27, 2024):

I can see the same issue with our installation on v4.0.6. In my configuration.py I have set CHANGELOG_RETENTION = 0. When I navigate to /core/config-revisions/add/ The field for the changelog retention is correctly greyed out and the value is 0. Looking at /core/system/ the value is displayed as 90 (the default I think).
We don't have any ConfigRevisions in our database.

@tobiasge commented on GitHub (Jun 27, 2024): I can see the same issue with our installation on v4.0.6. In my `configuration.py` I have set `CHANGELOG_RETENTION = 0`. When I navigate to `/core/config-revisions/add/` The field for the changelog retention is correctly greyed out and the value is 0. Looking at `/core/system/` the value is displayed as 90 (the default I think). We don't have any ConfigRevisions in our database.
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: medium 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#9885
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?