We're getting the following in the server-test pod during the test workflow:
------------------------------------------------------------------------------------------------------------------------
==> Logs of container openbao-zjqq3ibo8s-server-test
------------------------------------------------------------------------------------------------------------------------
Checking for sealed info in 'vault status' output
Attempt 0...
/bin/sh: line 6: vault: command not found
Attempt 1...
/bin/sh: line 6: vault: command not found
Attempt 2...
/bin/sh: line 6: vault: command not found
Attempt 3...
/bin/sh: line 6: vault: command not found
Attempt 4...
/bin/sh: line 6: vault: command not found
Attempt 5...
/bin/sh: line 6: vault: command not found
Attempt 6...
/bin/sh: line 6: vault: command not found
Attempt 7...
/bin/sh: line 6: vault: command not found
Attempt 8...
/bin/sh: line 6: vault: command not found
Attempt 9...
/bin/sh: line 6: vault: command not found
timed out looking for sealed info in 'vault status' output
Describe the bug
We're getting the following in the server-test pod during the test workflow:
Example job where it failed: https://github.com/openbao/openbao-helm/actions/runs/9165363410/job/25198629301#step:8:395
Environment
github workflow in this repo
Additional context
Pretty sure this is the smoking gun: https://github.com/openbao/openbao-helm/blob/b59b6e55bb124e6486f861feeb15c2428096634b/charts/openbao/templates/tests/server-test.yaml#L36
I assume we want this to be changed to
bao status
, yes? Correct me if I'm wrong. I haven't tried it yet :sweat_smile: