starred/netbox
1
0
Fork 0
mirror of https://github.com/netbox-community/netbox.git synced 2026-01-13 22:03:32 +01:00
Code Issues 273 Packages Projects Releases 10 Wiki Activity

Doesn't change time zone #9821

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

Originally created by @Hidmink on GitHub (Jun 9, 2024).

Originally assigned to: @arthanson on GitHub.

Deployment Type

Self-hosted

NetBox Version

v4.0.5

Python Version

3.12

Steps to Reproduce

  1. Change config file in '/opt/netbox/netbox/netbox/configuration.py' in SystemParametrs TIME_ZONE to any other timezone are not applied.

Expected Behavior

Applying settings TIME_ZONE in configuration file.

Observed Behavior

Apply defaults - UTC.

Originally created by @Hidmink on GitHub (Jun 9, 2024). Originally assigned to: @arthanson on GitHub. ### Deployment Type Self-hosted ### NetBox Version v4.0.5 ### Python Version 3.12 ### Steps to Reproduce 1. Change config file in '/opt/netbox/netbox/netbox/configuration.py' in SystemParametrs TIME_ZONE to any other timezone are not applied. ### Expected Behavior Applying settings TIME_ZONE in configuration file. ### Observed Behavior Apply defaults - UTC.
adam added the type: bugstatus: revisions needed labels 2025-12-29 21:23:10 +01:00
adam closed this issue 2025-12-29 21:23:10 +01:00
adam commented 2025-12-29 21:23:11 +01:00
Author
Owner
Copy Link

@arthanson commented on GitHub (Jun 10, 2024):

@Hidmink can you please add to the description where the timezone is not being applied? Is it in a display or when processing an event?

@arthanson commented on GitHub (Jun 10, 2024): @Hidmink can you please add to the description where the timezone is not being applied? Is it in a display or when processing an event?
adam commented 2025-12-29 21:23:11 +01:00
Author
Owner
Copy Link

@kuhball commented on GitHub (Jun 11, 2024):

Just noticed this as well while migrating our prod instance. For us the timezone is not applied within the ui (f.e. changelog).

@kuhball commented on GitHub (Jun 11, 2024): Just noticed this as well while migrating our prod instance. For us the timezone is not applied within the ui (f.e. changelog).
adam commented 2025-12-29 21:23:11 +01:00
Author
Owner
Copy Link

@PaulR282 commented on GitHub (Jun 11, 2024):

Same problem here. The right time is displayed on the bottom right but it is UTC in the changelog

@PaulR282 commented on GitHub (Jun 11, 2024): Same problem here. The right time is displayed on the bottom right but it is UTC in the changelog
adam commented 2025-12-29 21:23:11 +01:00
Author
Owner
Copy Link

@shaderecker commented on GitHub (Jun 11, 2024):

I also noticed the issue for Scheduled Scripts.
The displayed time of our Netbox in the bottom right is CEST.
However once I schedule a script it is always scheduled two hours earlier than selected in the UI. So it is scheduled in UTC.

@shaderecker commented on GitHub (Jun 11, 2024): I also noticed the issue for Scheduled Scripts. The displayed time of our Netbox in the bottom right is CEST. However once I schedule a script it is always scheduled two hours earlier than selected in the UI. So it is scheduled in UTC.
adam commented 2025-12-29 21:23:12 +01:00
Author
Owner
Copy Link

@arthanson commented on GitHub (Jun 13, 2024):

This looks like a dupe of #16143 this should be fixed in next release from change in #16323 . Closing

@arthanson commented on GitHub (Jun 13, 2024): This looks like a dupe of #16143 this should be fixed in next release from change in #16323 . Closing
adam commented 2025-12-29 21:23:12 +01:00
Author
Owner
Copy Link

@samk-acw commented on GitHub (Jul 1, 2024):

can this be reopened? https://github.com/netbox-community/netbox/pull/16323 appears to only have resolved the issue in table columns, the timezone is still inconsistent in multiple places in the interface:

For example, my server (running v4.0.6) is set to AEST and I took these screenshots around 12pm:

  • looking at an object change directly shows UTC:
    image

  • the created and updated timestamps on object views shows as UTC
    image

  • running scripts show both UTC and local
    image

I think the issue is the isodate/isodatetime filters don't load any timezone preference

@samk-acw commented on GitHub (Jul 1, 2024): can this be reopened? https://github.com/netbox-community/netbox/pull/16323 appears to only have resolved the issue in table columns, the timezone is still inconsistent in multiple places in the interface: For example, my server (running v4.0.6) is set to AEST and I took these screenshots around 12pm: - looking at an object change directly shows UTC: ![image](https://github.com/netbox-community/netbox/assets/55128650/12c2fc0f-2ae0-45cd-9b25-bb8cd547a95a) - the created and updated timestamps on object views shows as UTC ![image](https://github.com/netbox-community/netbox/assets/55128650/ea62100e-8b59-4f53-8c93-5a921ec67733) - running scripts show both UTC and local ![image](https://github.com/netbox-community/netbox/assets/55128650/f2abddd7-b990-4e45-83ff-fa38a3d48f08) I think the issue is the isodate/isodatetime filters don't load any timezone preference
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 status: revisions needed 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#9821
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?