Open Stack

 Controllers and haproxy are on KVM. We have 3 controllers. We used to have RMQ issues during KVM reboot but that stopped after we switched to durable queues. We expected to stop seeing customer impact after fixing the RMQ issues, but we still see it.
     On Thursday, May 11, 2023, 11:14:17 PM EDT, Satish Patel <satish.txt at gmail.com> wrote:  
 
 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/20230512/165d9625/attachment-0001.htm>