Comment 8 for bug 1565759

> ntp.conf from wrong configured node:
> https://paste.mirantis.net/show/2108/

It's not wrong, it's 100% correct. It's controller, and ntp.conf on controller nodes is configured by osnailyfacter/modular/ntp/ntp-server.pp manifest which uses `external_ntp` parameter from astute.yaml (in your case it's 10.109.15.1) as ntp server.

> ntp.cond from corectry configured node:
> https://paste.mirantis.net/show/2110/

It's non-controller node, so ntp.conf is configured by osnailyfacter/modular/ntp/ntp-client.pp manifest and it uses $management_vrouter_vip as ntp server (10.109.16.2 in your case).

> so it looks like the data in astute.yaml were corrupted after deployment one of noded

I've checked logs in your snapshot step-by-step, analyzed astute.yaml parameters uploaded to nodes and I see no data corruption (https://paste.mirantis.net/show/2124/). So please elaborate which data exactly is corrupted.