What I've discovered is asymmetrical network bridge configuration on nodes:
controller: root@node-2:~# cat /etc/astute.yaml | grep enp0s5 enp0s5: - {action: add-port, bridge: br-mgmt, name: enp0s5}
compute: root@node-1:~# cat /etc/astute.yaml | grep enp0s5 enp0s5: - {action: add-port, bridge: br-storage, name: enp0s5}
If I manually assign enp0s5 to br-mgmt ntpdate starts to work.
The test provisions nodes one by one using separate fuel cli commands. It might be that astule.yaml was mutated between these steps.
What I've discovered is asymmetrical network bridge configuration on nodes:
controller:
root@node-2:~# cat /etc/astute.yaml | grep enp0s5
enp0s5:
- {action: add-port, bridge: br-mgmt, name: enp0s5}
compute:
root@node-1:~# cat /etc/astute.yaml | grep enp0s5
enp0s5:
- {action: add-port, bridge: br-storage, name: enp0s5}
If I manually assign enp0s5 to br-mgmt ntpdate starts to work.
The test provisions nodes one by one using separate fuel cli commands. It might be that astule.yaml was mutated between these steps.