vault-job-init returns incorrect status

Bug

Description

When the vault-job-init job executes, it does not correctly interpret the return status of the "vault operator init" command.

This causes reported job failures even when the Vault service is running properly.

Provide any steps possible used to reproduce the error (ideally in an isolated fashion).

Deploy BB Vault into a k8s cluster. Redeploy BB Vault into the cluster without wiping the vault namespace's PVCs.

BigBang Version

What version of BigBang were you running? N/A; we do not use BigBang umbrella, we use BB Vault and other BB components.

Version 0.29.1-bb.5 of BB Vault.

changed the description

added community-contribution teamStorage & Collaboration labels

added triage-kind label

added triage-priority label

changed milestone to %2.48.0

changed iteration to Big Bang Iterations Feb 18, 2025 - Mar 3, 2025

added kindbug priority3 statusready-to-work labels

removed triage-kind label

removed triage-priority label

set weight to 3

assigned to @justinguidry11

added statusdoing label and removed statusready-to-work label

changed weight to 4 from 3

mentioned in merge request !224 (merged)

Addressing the reported interpretation of the mentioned line was relatively simple to fix but beyond that with the given situation, vault will likely be sealed and the init container script will be unable to progress. As far as I am aware, unsealing vault is to be done manually with the exceptions of KMS environments that can enable auto-unseal. But by documented design I believe this issue cannot be worked further beyond what has been performed.

added statusreview label and removed statusdoing label

Closing as of merging this MR: big-bang/bigbang!5832 (merged)

closed

removed statusreview label