oadp-1.4 periodic e2e (4.18 AWS): "Multiple BSL with custom CA cert" times out on "Default BSL should be available"

Aperta
  • Qualcosa non va?
#2,514 0 commenti 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

@kaovilai ci sta già lavorando.

Dal 22/10/2026.

  • #2515 di @kaovilai — aperta

Valutazione

Difficoltà
4/5
Tempo stimato
3-5 giorni
Idoneità per principianti
48/100
Tipo di issue
Bug
Chiarezza
Abbastanza chiara
Stato di attività
Attiva
Stack tecnologico
go
Ambito
testing

Direzione di ricerca

Start with the failing check at tests/e2e/backup_restore_suite_test.go:696 and the spec ending at line 741; inspect how it waits for the default BSL to become Available. Compare the CA cert and backupImages variants and review BSL validation timing on the 1.4/4.18 AWS run. Done when the cause of the timeout is identified and the spec succeeds reliably within an appropriate wait period.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

Summary

periodic-ci-openshift-oadp-operator-oadp-1.4-4.18-e2e-test-aws-periodic has failed 12 of its last 20 runs (Oct 1–22). The recurring failure is in the Multiple BSL with custom CA cert tests, not the S3 GetBucketRegion blip tracked in openshift/oadp-operator#2512.

Evidence (periodic job, oadp-1.4, 4.18 AWS)

Run date Failing spec
Oct 9 Multiple BSL with custom CA cert: three BSLs with backupImages=false (+5 other failures)
Oct 10 three BSLs with backupImages=true (full CA cert handling with concat)
Oct 12 three BSLs with backupImages=false (no CA cert handling)
Oct 18 three BSLs with backupImages=false (no CA cert handling)
Oct 19 three BSLs with backupImages=false (no CA cert handling)

Failure signature (Oct 18):

[FAILED] Timed out after 180.003s.
Default BSL should be available
Expected <bool>: false to be true
In [It] at: tests/e2e/backup_restore_suite_test.go:696
Exit [It] three BSLs with backupImages=false (no CA cert handling) - backup_restore_suite_test.go:741 (3m21s)

Oct 18 run: https://prow.ci.openshift.org/view/gs/test-platform-results/logs/periodic-ci-openshift-oadp-operator-oadp-1.4-4.18-e2e-test-aws-periodic/2111668852025724928

Not covered here

  • The Oct 20 nil-pointer panic in BSLsAreUpdated (tests/e2e/lib/dpa_helpers.go:304) already has fixes: openshift/oadp-operator#2499, openshift/oadp-operator#2500, openshift/oadp-operator#2502.
  • The S3 region lookup blip (Oct 3, Oct 8, Oct 21): openshift/oadp-operator#2512, plus a retry fix to follow.

To investigate

  • Why the default BSL never reaches Available within 180s in this spec on 1.4/4.18: CA cert / backupImages handling, BSL validation timing, or the test's own wait.
  • Whether the same spec is flaky on other branches/versions or only 1.4.
  • Whether the 180s timeout is too tight for this job's cluster speed (the full e2e takes about 85 min).

[!Note]
Responses generated with Claude (model: Claude Sonnet 5.5)

Lingua principale
Go
Stelle
93
Fork
93
Merge medio
1g 16h
PR unite (30g)
25

Preparare l'ambiente

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di openshift/oadp-operator

Tutte le issue di openshift/oadp-operator

Issue simili

Altre issue su Go

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.