I've uploaded a cloud-init test package to a ppa; you can test that this update fixes the ntp issue on an existing node.
On an affected node:
1. sudo add-apt-repository -y ppa:raharper/bugfixes 2. sudo apt update && sudo apt install cloud-init (#installs 0.7.9-6-gf5fdb6c-1~bddeb) 3. cat >user-data << EOF #cloud-config
ntp: servers: - 17.16.18.19 - 17.16.15.14 pools: - 0.cloud-init.mypool EOF 4. cloud-init --file user-data single --report --name ntp --frequency always 5. ntpq -p -w
You should see that ntp.conf has been updated with the supplied servers and pool, and that ntpq output shows those servers/pools.
I've uploaded a cloud-init test package to a ppa; you can test that this update fixes the ntp issue on an existing node.
On an affected node:
1. sudo add-apt-repository -y ppa:raharper/ bugfixes gf5fdb6c- 1~bddeb)
2. sudo apt update && sudo apt install cloud-init (#installs 0.7.9-6-
3. cat >user-data << EOF
#cloud-config
ntp:
servers:
- 17.16.18.19
- 17.16.15.14
pools:
- 0.cloud-init.mypool
EOF
4. cloud-init --file user-data single --report --name ntp --frequency always
5. ntpq -p -w
You should see that ntp.conf has been updated with the supplied servers and pool, and that ntpq output shows those servers/pools.