Implement/update time sync logic for CI (system tests)
Bug #1320815 reported by
Bogdan Dobrelya
This bug affects 2 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Fuel for OpenStack |
Fix Released
|
Critical
|
Fuel QA Team |
Bug Description
Please ensure for every reverting from the snapshots the following steps os executed as well:
1) Sync time at the master node host OS
ntpdate -u pool.ntp.org
2) Enter to the docker container shell for astute
dockerctl shell astute
3) use mco rexec plugin to issue time sync for all nodes in the manged enviromnents
mco rpc -v execute_
Note: use any similar commands you want, just make sure the time would be in sync prior to the starting deploy anything.
Changed in fuel: | |
assignee: | nobody → Fuel QA Team (fuel-qa) |
description: | updated |
description: | updated |
Changed in fuel: | |
status: | Confirmed → Triaged |
Changed in fuel: | |
importance: | High → Critical |
To post a comment you must log in.
If desync is large, MCollective won't be able to run its agents. So I believe that more reliable solution is to ssh from systests onto each node and run those commands.