Need to synchronize time on nodes with master-node during deployment
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Fuel for OpenStack |
Fix Committed
|
High
|
Vladimir Sharshov |
Bug Description
"build_id": "2014-03-
"mirantis": "yes",
"build_number": "40",
"nailgun_sha": "3044c205490452
"ostf_sha": "013c13ab033a68
"fuelmain_sha": "f7ee8bcaa3d993
"astute_sha": "d7c6c4d00ffd6e
"release": "5.0",
"fuellib_sha": "3445ab75504860
1. Create new environment (Ubuntu, simple node)
2. Choose both of ceph
3. Add controller, 3 compute+ceph
4. Start deployment. It was successful
5. But nova-network in XXX state on all of computes because date was different from master-node
root@node-13:~# nova-manage service list
Binary Host Zone Status State Updated_At
nova-consoleauth node-13 internal enabled :-) 2014-03-25 13:24:10
nova-cert node-13 internal enabled :-) 2014-03-25 13:24:13
nova-scheduler node-13 internal enabled :-) 2014-03-25 13:24:12
nova-conductor node-13 internal enabled :-) 2014-03-25 13:24:07
nova-network node-14 internal enabled XXX 2014-03-25 13:18:10
nova-compute node-14 nova enabled :-) 2014-03-25 13:24:12
nova-network node-15 internal enabled XXX 2014-03-25 13:25:18
nova-network node-16 internal enabled XXX 2014-03-25 13:18:10
nova-compute node-15 nova enabled :-) 2014-03-25 13:23:36
nova-compute node-16 nova enabled :-) 2014-03-25 13:24:13
Need to synchronize time on nodes with master-node during deployment
Changed in fuel: | |
status: | New → Triaged |
tags: | added: low-hanging-fruit |
Changed in fuel: | |
importance: | Undecided → Medium |
Changed in fuel: | |
milestone: | 5.0 → 5.1 |
Changed in fuel: | |
importance: | Medium → High |
I'm often seeing this kind of problem when reverting a virtual fuel master from a snapshot. If master updates its clock after booting some slave nodes into bootstrap, these nodes will have their clock out of sync with the rest of the cluster. I found that forcing a time update on fuel master node with "service ntpd restart" before starting slave nodes into bootstrap helps. After about a minute, clock on the fuel master VM is in synch with the host, and all nodes booted after that remain in sync.