Doesn't change time zone

[Hidmink]

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.

[arthanson]

@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?

[kuhball]

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

[PaulR282]

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

[shaderecker]

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.

[arthanson]

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

[samk-acw]

can this be reopened? #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:
  

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

• running scripts show both UTC and local
  

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