Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Scheduled Jobs Timezone bug #17108

Closed
ridgfam opened this issue Aug 9, 2024 · 2 comments · Fixed by #17267
Closed

Scheduled Jobs Timezone bug #17108

ridgfam opened this issue Aug 9, 2024 · 2 comments · Fixed by #17267
Assignees
@bctiemann
Labels
severity: low Does not significantly disrupt application functionality, or a workaround is available status: accepted This issue has been accepted for implementation type: bug A confirmed report of unexpected behavior in the application

Comments

@ridgfam
Copy link

ridgfam commented Aug 9, 2024

Deployment Type

Self-hosted

NetBox Version

v4.0.8

Python Version

3.10

Steps to Reproduce

  1. Select Script
  2. Put date and time in Schedule at
    scheduleScript
  3. Click Run Script

Expected Behavior

Expected it to show as MDT.

Observed Behavior

Shows as UTC instead of MDT
scriptScheduled
@ridgfam ridgfam added status: needs triage This issue is awaiting triage by a maintainer type: bug A confirmed report of unexpected behavior in the application labels Aug 9, 2024
@arthanson arthanson added status: needs owner This issue is tentatively accepted pending a volunteer committed to its implementation severity: low Does not significantly disrupt application functionality, or a workaround is available and removed status: needs triage This issue is awaiting triage by a maintainer labels Aug 9, 2024
@arthanson arthanson assigned arthanson and unassigned arthanson Aug 9, 2024
@arthanson arthanson added status: accepted This issue has been accepted for implementation and removed status: needs owner This issue is tentatively accepted pending a volunteer committed to its implementation labels Aug 13, 2024
@arthanson arthanson removed their assignment Aug 13, 2024
@arthanson arthanson added status: needs owner This issue is tentatively accepted pending a volunteer committed to its implementation and removed status: accepted This issue has been accepted for implementation labels Aug 13, 2024
@jeremystretch
Copy link
Member

When I schedule a script for a specific time, that time is interpreted by NetBox as the configured time zone (UTC). But in your case it appears to be interpreted in the local time zone and converted to UTC.

@ridgfam what is your TIME_ZONE config parameter set to?

@ridgfam
Copy link
Author

ridgfam commented Aug 13, 2024

That is set TIME_ZONE = 'America/Denver'

@jeremystretch jeremystretch added status: accepted This issue has been accepted for implementation and removed status: needs owner This issue is tentatively accepted pending a volunteer committed to its implementation labels Aug 26, 2024
@bctiemann bctiemann mentioned this issue Aug 26, 2024
Merged
jeremystretch pushed a commit that referenced this issue Aug 26, 2024
@bctiemann
Fixes: #17108 - Update isotime and isodate filters to be timezone-awa…
1d2ea90 
…re (#17267)

* Update isotime and isodate filters to be timezone-aware for display in templates (particularly Scripts)

* Handle naive datetimes gracefully
@jeremystretch jeremystretch mentioned this issue Aug 29, 2024
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@bctiemann bctiemann

Labels
severity: low Does not significantly disrupt application functionality, or a workaround is available status: accepted This issue has been accepted for implementation type: bug A confirmed report of unexpected behavior in the application
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Fixes: #17108 - Update isotime and isodate filters to be timezone-aware netbox-community/netbox
4 participants
@arthanson @bctiemann @jeremystretch @ridgfam