Add real_time_clock_utc option to cloudbase_init_conf (default=False)#471
Merged
Conversation
Dany9966
requested changes
Jul 14, 2026
fabi200123
force-pushed
the
fix-timing-issue
branch
from
July 14, 2026 13:45
1b04819 to
b9f4bd9
Compare
fabi200123
force-pushed
the
fix-timing-issue
branch
from
July 15, 2026 06:51
b9f4bd9 to
b84648d
Compare
Dany9966
approved these changes
Jul 15, 2026
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
This PR adds the option to configure
real_time_clock_utcin the cloudbase-init config (default value isFalse, as per cloudbase-init docs) to fix issues when Windows VMs are migrated and the time is changes to UTC for a few moments.The issues were seen when migrating Windows VMs to LXD, and the VM was firstly setting time to UTC and just after a few moments, it got changed back to what was on the source.