Change to openbao breaking change, Error 473
- https://github.com/hashicorp/vault-client-go/blob/315a2bfeef6c799e72f31543f5bbe38284ca777b/CHANGELOG.md?plain=1#L65
- 63f4c9de Gitlab Runner commit
- https://github.com/hashicorp/vault-client-go/blob/315a2bfeef6c799e72f31543f5bbe38284ca777b/errors.go#L71
- https://developer.hashicorp.com/vault/api-docs/system/health#473
- https://github.com/openbao/openbao/blob/6d1e0edaf167fac0bc122dd956bb5a439d8782ed/http/sys_health.go#L77
See the following references above.
Vault returns 473 error on /sys/health endpoint and it should not be treated as an error.
The openbao library does not make this exception and our runner jobs are now failing on this vault error.
Confirmed that the change made it into 18.3 release.
Running with gitlab-runner 18.3.0 (9ba718cd)
on XXXXX CF8Rrgh2d, system ID: s_70f505123a7b
feature flags: FF_USE_FASTZIP:true, FF_GIT_URLS_WITHOUT_TOKENS:true
Resolving secrets
Resolving secret "XXXXX_SSH_KEY"...
Using "vault" secret resolver...
ERROR: Job failed (system failure): resolving secrets: initializing Vault service: preparing authenticated client: checking Vault server health: api error: status code 473: Edited by Cyprian Bergonia