Cloud vault LoadBalancer send write requests to stabdby nodes in vault cluster when we use cluster endpoint for connections

incoming requests balanced betwen nodes and one node with standby:false another with standby:true for example:
% curl https://relic--prod.vault.62-48c4-a50d-61d66f2c9bd5.aws.hashicorp.cloud:8200/v1/sys/health

{"initialized":true,"sealed":false,"standby":true,"performance_standby":true,"replication_performance_mode":"disabled","replication_dr_mode":"disabled","server_time_utc":1627398653,"version":"1.7.3+ent","cluster_name":"vault-cluster-****","cluster_id":"****-520f-a5e1-f6bc-ce3cc229a2da"}

% curl https://relic--prod.vault.62-48c4-a50d-61d66f2c9bd5.aws.hashicorp.cloud:8200/v1/sys/health

{"initialized":true,"sealed":false,"standby":false,"performance_standby":false,"replication_performance_mode":"disabled","replication_dr_mode":"disabled","server_time_utc":1627398656,"version":"1.7.3+ent","cluster_name":"vault-cluster-****","cluster_id":"4*****-520f-a5e1-f6bc-ce3cc229a2da","last_wal":46139}

that’s provide to an issue:
“error performing token check: failed to persist lease entry: cannot write to readonly storage”

1 Like

We need an urgent solution to this issue! we cannot launch our product in time because of this strange error. If anyone managed to overcome this please share your resolution.

the same issue has been posted 1 year ago and it was apparently solved 1.5.4 - however many people still having issues on later versions including 1.7.3

i do not understand why this is being overlooked by hashicorp. this is a serious issue!!!