Windows agent doesn't reconnect to the new master after cluster failover

Description

That's been an ongoing issue for a while now, however no ticket was opened for it.
Whenever there is an HA failover, Windows agents don't connect to the new master.
The Windows agent needs to be restarted.
This doesn't happen on Linux.

Our action items:
1. Build an environment, using HA-Proxy as a VIP
2. Attempt to replicate the issue
2.1 If successful, then... fix it.
2.2 Otherwise, the problem may have something to do with customer's VIP and how our Windows Python libraries communicate with it. Troubleshooting would require collaboration with the customer people to trace traffic to/from the VIP.

Steps to Reproduce

Environment:
OS (CLI), HA cluster, cloud provider
------------------------------------

Steps to reproduce:
------------------
1.
2.
3.

Expected result:
---------------

Actual result:
-------------

Why Propose Close?

None

Activity

Show:
Alex Molev
August 31, 2020, 10:38 AM

had a call with on Thursday and they validated that there is now issue with reconnecting.

The issue they had is windows going to hibernate mode.

you can close this one

geokala
August 31, 2020, 10:45 AM

Fantastic, I was just setting up the proxy but I’ll burn it down now.

Assignee

geokala

Reporter

Alex Molev

Labels

None

Severity

High

Target Version

4.6

Premium Only

yes

Found In Version

4.6

QA Owner

None

Bug Type

legacy bug

Customer Encountered

Yes

Customer Name

c312

Release Notes

no

Priority

High

Epic Link

Sprint

None

Priority

Critical
Configure