Comment 4 for bug 1417922

Revision history for this message
Artem Panchenko (apanchenko-8) wrote : Re: [BVT] Clock skew detected for Ceph after snapshot revert

@Stanislaw,

this issue is still reproduced on bvt:

http://jenkins-product.srt.mirantis.net:8080/job/6.1.ubuntu.bvt_2/96/console
http://jenkins-product.srt.mirantis.net:8080/job/6.1.ubuntu.bvt_2/95/console

This bug was marked as duplicate of https://bugs.launchpad.net/fuel/+bug/1415596 , but it's a separate issue because time synchronization (on master and bootstrapped slaves) after reverting from snapshot was successful:

http://paste.openstack.org/show/167406/

Then tests deployed a cluster, found that Ceph health is bad (Clock skew detected) and synced (successfully) time to fix that:

http://paste.openstack.org/show/167407/

but it didn't help (test was waiting for Ceph health recovery 6 minutes):

2015-02-05 12:06:14,979 - DEBUG __init__.py:50 -- Done: get_ceph_health with result: HEALTH_WARN clock skew detected on mon.node-5, mon.node-6

In my opinion time wasn't correctly synchronized after provisioning before Ceph was deployed. I've found these NTP errors in logs on nodes:

http://paste.openstack.org/show/167429/