Host system should have time synced during deployment to prevent deployment issues.
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
tripleo |
Fix Released
|
Medium
|
Alex Schultz |
Bug Description
We've encountered a number of issues caused by the *host* machine being out of time sync (even in deployments when we provided correct NtpServer parameter to the overcloud Heat stack).
It seems that when virtual machines start, they get clock set by the hypervisor. This persists until the VM does its own NTP sync, and until then it can cause a variety of "headscratcher" issues which are very difficult to debug and comprehend, usually ones which one person is able to reproduce fairly consistently, but others don't hit them ever.
I'm not sure if Quickstart itself should be in charge of setting up NTP sync on the host machine (maybe?) but i think it should at least refuse to run if NTP is not synced.
summary: |
- [RFE] quickstart should validate that *host* machine is NTP synced + [RFE] quickstart should validate that host machine is NTP synced |
I hit issues related to the UC backup/restore because of sync issues. Would be a good thing to have.