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

tzdata error 'No time zone found with key America/Ciudad_Juarez' #7404

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

Originally created by @nicoovh on GitHub (Dec 21, 2022).

NetBox version

v3.3.8

Python version

3.9

Steps to Reproduce

  1. pip install -r requirements.txt
  2. launch manage.py migrate with a plugin that has date related fields
  3. error happens:
    zoneinfo._common.ZoneInfoNotFoundError: 'No time zone found with key America/Ciudad_Juarez'

seems related to many previous raised bugs, usually fixed by pinning tzdata in requirements.txt
due to the new release of tzdata/pytz 2022.7

Expected Behavior

application shall not crash

Observed Behavior

application crash

Originally created by @nicoovh on GitHub (Dec 21, 2022). ### NetBox version v3.3.8 ### Python version 3.9 ### Steps to Reproduce 1. pip install -r requirements.txt 2. launch manage.py migrate with a plugin that has date related fields 3. error happens: ``zoneinfo._common.ZoneInfoNotFoundError: 'No time zone found with key America/Ciudad_Juarez'`` seems related to many previous raised bugs, usually fixed by pinning tzdata in requirements.txt due to the new release of tzdata/pytz 2022.7 ### Expected Behavior application shall not crash ### Observed Behavior application crash
adam closed this issue 2025-12-29 20:23:00 +01:00
adam commented 2025-12-29 20:23:00 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Dec 22, 2022):

launch manage.py migrate with a plugin that has date related fields

I'm afraid we can't accept such a vague bug report. If you're able to reproduce the reported behavior in NetBox itself, please update your description above and I'll be happy to reopen it. However, if this bug is related to the installation of a particular plugin, you'll need to submit a bug report to its maintainer.

@jeremystretch commented on GitHub (Dec 22, 2022): > launch manage.py migrate with a plugin that has date related fields I'm afraid we can't accept such a vague bug report. If you're able to reproduce the reported behavior in NetBox itself, please update your description above and I'll be happy to reopen it. However, if this bug is related to the installation of a particular plugin, you'll need to submit a bug report to its maintainer.
adam commented 2025-12-29 20:23:00 +01:00
Author
Owner
Copy Link

@cpmills1975 commented on GitHub (Jan 6, 2023):

I've hit this issue today trying to run vanilla NetBox 3.2.8 in the official python:3.11 container (I'm trying to write some unit tests for my own plugin code). While it's likely an issue with the container/python installation more than it is NetBox, installing tzdata==2022.7 as suggested did fix it and pinning it in requirements.txt would be a minor change I'd suggest.

@cpmills1975 commented on GitHub (Jan 6, 2023): I've hit this issue today trying to run vanilla NetBox 3.2.8 in the official python:3.11 container (I'm trying to write some unit tests for my own plugin code). While it's likely an issue with the container/python installation more than it is NetBox, installing tzdata==2022.7 as suggested did fix it and pinning it in requirements.txt would be a minor change I'd suggest.
adam commented 2025-12-29 20:23:01 +01:00
Author
Owner
Copy Link

@Millnert commented on GitHub (Jan 11, 2023):

Hit the same issue while updating from 3.0.1 towards 3.4.2 (through 3.1.0, 3.2.0, 3.3.4), no plugins present. It hit on the 3.2.0 (tzdata=2022.1) and 3.3.4 step (tzdata=2022.2). bumping tzdata from 2022.1/2022.2 to 2022.7 in requirements.txt solved the problem here as well.

@Millnert commented on GitHub (Jan 11, 2023): Hit the same issue while updating from 3.0.1 towards 3.4.2 (through 3.1.0, 3.2.0, 3.3.4), no plugins present. It hit on the 3.2.0 (tzdata=2022.1) and 3.3.4 step (tzdata=2022.2). bumping tzdata from 2022.1/2022.2 to 2022.7 in requirements.txt solved the problem here as well.
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
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#7404
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?