Regarding the HA VIP assignment. On a fresh deploy of 1.24 we had this happen with 2 openstack services. For example with glance: https://pastebin.canonical.com/133635/ where 172.20.168.102 is our VIP. Interestingly on this run the config-changed hook error and VIP assignment appear to have happened about 30 minutes after the deploy completed but unfortunately I did not capture a paste of this in a non-errored state or when it exactly happened so I absolutely could have missed something there. Full logs from all 3 metals, the resultant glance corosync.conf files, and sosreports from all 3 metals are at https://chinstrap.canonical.com/~jillr/lp1463480/. Our bundle and deploy script are also there. The addressing of all glance units in this deploy: https://pastebin.canonical.com/133640/
Regarding the HA VIP assignment. On a fresh deploy of 1.24 we had this happen with 2 openstack services. For example with glance: https:/ /pastebin. canonical. com/133635/ where 172.20.168.102 is our VIP. Interestingly on this run the config-changed hook error and VIP assignment appear to have happened about 30 minutes after the deploy completed but unfortunately I did not capture a paste of this in a non-errored state or when it exactly happened so I absolutely could have missed something there. Full logs from all 3 metals, the resultant glance corosync.conf files, and sosreports from all 3 metals are at https:/ /chinstrap. canonical. com/~jillr/ lp1463480/. Our bundle and deploy script are also there. The addressing of all glance units in this deploy: https:/ /pastebin. canonical. com/133640/