[kolla] [train] haproxy and controller restart causes user impact
Satish Patel
satish.txt at gmail.com
Fri May 12 03:04:06 UTC 2023
Are you running your stack on top of the kvm virtual machine? How many
controller nodes do you have? mostly rabbitMQ causing issues if you restart
controller nodes.
On Thu, May 11, 2023 at 8:34 AM Albert Braden <ozzzo at yahoo.com> wrote:
> We have our haproxy and controller nodes on KVM hosts. When those KVM
> hosts are restarted, customers who are building or deleting VMs see impact.
> VMs may go into error status, fail to get DNS records, fail to delete, etc.
> The obvious reason is because traffic that is being routed to the haproxy
> on the restarting KVM is lost. If we manually fail over haproxy before
> restarting the KVM, will that be sufficient to stop traffic being lost, or
> do we also need to do something with the controller?
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.openstack.org/pipermail/openstack-discuss/attachments/20230511/71a3db27/attachment.htm>
More information about the openstack-discuss
mailing list