Investigate failed tests for velero
Bug
Velero tests are failing on clean install
and upgrade
Description
Velero tests fail in the bigbang pipeline, but not in the velero package pipeline. Detailed logs are included below.
BigBang Version
2.17.0 (velero version 5.1.6-bb.0)
Logs
Example of a failed pipeline: https://repo1.dso.mil/big-bang/bigbang/-/jobs/29718421#L3675
---
Running backup-restore.sh...
---
+ trap 'echo ❌ exit at ${0}:${LINENO}, command was: ${BASH_COMMAND} 1>&2' ERR
+ echo 'Setup 1: Ensuring MinIO endpoint up and available'
+ curl -sIS https://minio-api.bigbang.dev
Setup 1: Ensuring MinIO endpoint up and available
+ [[ '' == \t\r\u\e ]]
+ echo 'Setup 1 Success: MinIO is up.'
+ echo 'Setup 2: Create MinIO Bucket'
+ attempt_counter=0
+ max_attempts=25
Setup 1 Success: MinIO is up.
Setup 2: Create MinIO Bucket
++ mc config host add test https://minio-api.bigbang.dev minio minio123
++ echo 0
+ '[' 0 -eq 0 ']'
++ mc ls test/velero
mc: <ERROR> Unable to list folder. Bucket `velero` does not exist.
++ echo 1
+ '[' 1 -eq 0 ']'
+ mc mb test/velero
Bucket created successfully `test/velero`.
+ mc policy --insecure set public test/velero
mc: Please use 'mc anonymous'
+ echo 'Setup 2 Success: MinIO Bucket Created'
+ echo 'Setup 3: Creating test pod'
Setup 2 Success: MinIO Bucket Created
Setup 3: Creating test pod
+ cat
+ kubectl apply -f -
The connection to the server localhost:8080 was refused - did you specify the right host or port?
++ echo $'\342\235\214' exit at ./backup-restore.sh:40, command was: kubectl apply -f -
❌ exit at ./backup-restore.sh:40, command was: kubectl apply -f -
OK
---
Finished running all helm tests.
❌ Encountered 1 package(s) with errors while running tests. See output logs for failed test(s) above and artifacts in the job.
Edited by Noah Birrer