Time failed to sync on same nodes for different tests in random order
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Fuel for OpenStack |
Fix Released
|
Medium
|
Fuel QA Team | ||
6.1.x |
Won't Fix
|
Medium
|
Fuel QA Team | ||
8.0.x |
Won't Fix
|
Medium
|
Fuel QA Team | ||
Mitaka |
Fix Released
|
Medium
|
Fuel QA Team |
Bug Description
There is no steps how to reproduce this issue, but sometimes sync time failed in different tests for 1 of the nodes. It is may happens one time in 20 attempts, but if it happens, test became failed.
Provision new cluster many times after deletion the old one
Scenario:
1. Create HA cluster
2. Add 1 controller, 2 compute and 2 cinder nodes
3. Deploy the cluster
4. Delete cluster
5. Create another HA cluster
6. Create snapshot of environment
7. Revert snapshot and try provision cluster 10 times
Time on nodes was not synchronized:
[('node-3', [])]
Traceback (most recent call last):
File "/usr/lib/
testMethod()
File "/usr/lib/
self.
File "/home/
compatabili
File "/home/
func()
File "/home/
func(
File "/home/
result = func(*args, **kwargs)
File "/home/
self.
File "/home/
self.
File "/home/
return func(*args, **kwargs)
File "/home/
g_ntp.
File "/home/
" \n{0}".
File "/home/
raise ASSERTION_
AssertionError: Time on nodes was not synchronized:
[('node-3', [])]
Changed in fuel: | |
status: | New → Confirmed |
tags: | added: non-release |
Changed in fuel: | |
status: | Fix Committed → Fix Released |
tags: | removed: swarm-blocker |
Tag "swarm-blocker" was added because issue is cause of many failures on SWARM, see duplicate.