'ntpd' on controllers is configured to access itself as a remote peer
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Fuel for OpenStack |
Fix Released
|
Critical
|
Oleksiy Molchanov | ||
6.1.x |
Fix Committed
|
High
|
Alexey Stupnikov |
Bug Description
'ntpd' on all controllers is configured to access the vip__management IP as a remote peer.
Thus, the time on controllers and other remote nodes is never synchronized to external clock source.
root@node-1:~# ip netns exec vrouter ip r | grep vr-mgmt
10.109.12.0/24 dev vr-mgmt proto kernel scope link src 10.109.12.2
root@node-1:~# fgrep 'server' /etc/ntp.conf
server 10.109.12.2 iburst minpoll 3
Reproduced on swarm tests: http://
ISO version: {u'build_id': u'2015-
Changed in fuel: | |
status: | New → Confirmed |
Changed in fuel: | |
assignee: | Fuel Library Team (fuel-library) → Oleksiy Molchanov (omolchanov) |
tags: | added: fuel-to-mos |
Changed in fuel: | |
status: | Confirmed → Incomplete |
tags: | added: swarm-blocker |
Changed in fuel: | |
assignee: | Fuel Library Team (fuel-library) → Bogdan Dobrelya (bogdando) |
Changed in fuel: | |
assignee: | Bogdan Dobrelya (bogdando) → Oleksiy Molchanov (omolchanov) |
Strange, the config was changed by task ntp-client.conf that run in post-deploy. But it is not supposed to be executed on controller nodes. Python team, please take a look.