Olivier Bourdon

 

Doing a `git diff tag-v1.10.7..tag-v1.11.0 -- vault/ha.go` show the [following code](https://github.com/hashicorp/vault/blob/v1.11.0/vault/ha.go#L188:L195) which seems to be the source of the issue with the corresponding commit [106f548a41c5aa3a7310e1b53f2196f989913eff](https://github.com/hashicorp/vault/commit/106f548a41c5aa3a7310e1b53f2196f989913eff) Commenting out the [return line...

May be the test `if adv.ClusterAddr == c.ClusterAddr() && adv.RedirectAddr == c.redirectAddr {` is just incomplete as in the comment it is said that `if we are the active node`...

``` $ dig +short vault.internal.mycluster.io 10.0.15.206 10.0.36.214 10.0.19.203 ``` and therefore ``` RedirectAddr:https://vault.internal.mycluster.io ClusterAddr:https://vault.internal.mycluster.io:444 ``` in the received JSON advertisement structure and the same "addresses" are in the Core structure

As a first suggestion of what could be a more complete test which might solve the issue is to do a `url.ParseRequestURI` on the string. If this fails, then comparison...

@ccapurso many thanks for categorising this

AFAICT I do not think that having DynamoDB as the vault backend has anything to do with the issue. I am pretty much sure I can reproduce this with Raft...

@ArchiFleKs on my side with a working HA cluster (Vault = 1.11.0 and relaunch the associated Linux service then run the command `curl http://127.0.0.1:8200/v1/sys/leader` on the modified node and I...

@ArchiFleKs seems like it should be working perfectly like 1.10.7 (at least it does not include the failing 1.11.0 code)

I do not see any activity on this huge regression issue. Can someone please take care of this ?