We're updating the issue view to help you get more done. 

Connection failed to active manager after second manager failed to join

Description

Steps to reproduce:
1. Start cluster from manager m1
2. Join cluster from manager m2. at the middle of the join process stop the process with keyboard interrupt.
3. Wait until the managers are stable
4. Set-active m2 to become the leader-manager in the cluster
5. Try to connect back to m1 or m2

The cli fails to connect any of the managers after the join-failure process. I would expect that even after join-cluster failure, m1 will still be the active manager, which I can connect to

Status

Assignee

Łukasz Maksymczuk

Reporter

Uri Wygodny

Labels

Severity

None

Bug Type

regression bug

Target Version

4.3

Severity

None

Epic Link

Sprint

None

Fix versions

Affects versions

4.3