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.

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

unknown time zone Europe/Amsterdam #2284

Closed
Jille opened this issue Sep 11, 2021 · 4 comments · Fixed by #2285
Closed

unknown time zone Europe/Amsterdam #2284

Jille opened this issue Sep 11, 2021 · 4 comments · Fixed by #2285
Labels
kind/bug Categorizes issue or PR as related to a bug.

Comments

@Jille
Copy link

Jille commented Sep 11, 2021

What happened:

I was migrating from Google Cloud DNS to TransIP with a new domain name, and it stopped working.

These three log lines keep repeating. I'm assuming the first one is the real problem and the others are just noise.

time="2021-09-11T09:03:30Z" level=error msg="unknown time zone Europe/Amsterdam"
W0911 09:03:44.296169       1 transport.go:288] Unable to cancel request for *instrumented_http.Transport
W0911 09:04:14.299905       1 transport.go:288] Unable to cancel request for *instrumented_http.Transport

No DNS records were added.

What you expected to happen:

I hoped it'd add all our subdomains to the new domain at TransIP.

How to reproduce it (as minimally and precisely as possible):

I'm not doing anything special, so I suppose just using external-dns with TransIP and maybe a .nl domain name?

Anything else we need to know?:

I wasn't able to figure out where the "unknown time zone Europe/Amsterdam" error message was even coming from.

Environment:

  • External-DNS version (use external-dns --version): 0.9.0
  • DNS provider: TransIP
  • Others:
@Jille Jille added the kind/bug Categorizes issue or PR as related to a bug. label Sep 11, 2021
@Jille
Copy link
Author

Jille commented Sep 11, 2021

We patched the docker container by adding RUN apk --no-cache add tzdata and that solved the problem.

@Jille
Copy link
Author

Jille commented Sep 13, 2021

Someone else ran into this issue too and filed it on the gotransip side: transip/gotransip#31

@Owemeone
Copy link

Owemeone commented Mar 4, 2023

Since #2285 has been reverted, seems like this issue has returned. Could this be reopened?

@SimeonPoot
Copy link

+1 @Owemeone, running into this problem as well.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/bug Categorizes issue or PR as related to a bug.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants