Add Berlin timezone for container deployment. #1753
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
srbarrios
reviewed
Dec 9, 2024
Comment on lines
+41
to
+42
| tz: | ||
| Europe/Berlin |
There was a problem hiding this comment.
OK. But.. I'd have choose UTC, if that is available.
Also, did you double-check if that could affect to our environment deployed in other timezones like SLC?
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What does this PR change?
Currently, the container have a different timezone than server host or controller.
This differences are created some issues (getting the last log not working with the testsuite, using spacewalk is scheduling the event one hour later, etc)
Force the timezone to Berlin timezone.
Related to: https://github.com/SUSE/spacewalk/issues/25607