Noticed that we now call check-containers as part of upgrade, so this is probably no longer an issue on master. In ussuri it seems like to rely on a change in config.yml to restart the container. When there are no changes to the config files it doesn't get triggered. I'm running on an environment with a single host, but it seems like backup keepalived instances would be restarted due to:
Noticed that we now call check-containers as part of upgrade, so this is probably no longer an issue on master. In ussuri it seems like to rely on a change in config.yml to restart the container. When there are no changes to the config files it doesn't get triggered. I'm running on an environment with a single host, but it seems like backup keepalived instances would be restarted due to:
https:/ /github. com/openstack/ kolla-ansible/ blob/stable/ ussuri/ ansible/ roles/haproxy/ tasks/upgrade. yml#L15