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

Timezone in recover vm is UTC (and not CET) #47

Closed
gdha opened this issue Dec 8, 2017 · 3 comments
Closed

Timezone in recover vm is UTC (and not CET) #47

gdha opened this issue Dec 8, 2017 · 3 comments
Assignees
Labels
Milestone

Comments

@gdha
Copy link
Owner

gdha commented Dec 8, 2017

Test results at https://gist.github.com/206d14ff39eef8f9aebc82f2ae647e32 proofs that the recover vm is still one hour behind albeit ntpdate did work and corrected the time. However, the timezone is UTC instead of the CET which was defined in the client and server vm.
We still need to correct this in some way.

@gdha gdha added the bug label Dec 8, 2017
@gdha gdha added this to the v1.2 milestone Dec 8, 2017
@gdha gdha self-assigned this Dec 8, 2017
@gdha
Copy link
Owner Author

gdha commented Dec 8, 2017

See also rear/rear#1635

@gdha
Copy link
Owner Author

gdha commented Feb 17, 2018

@gdha
Copy link
Owner Author

gdha commented Feb 21, 2018

Problem has been solved via PR rear/rear#1734
Proof: https://gist.github.com/gdha/cda26d43c4cc255c573a22a64af136a5

@gdha gdha closed this as completed Feb 21, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant