Hacktoberfest 2026: le issue che i maintainer hanno segnato per ottobre, aperte e adatte ai principianti. Sfoglia le issue Hacktoberfest

Track intermittent empty sha256sum output in virt/KDM incremental CBT E2E

Aperta
  • Qualcosa non va?
#2,468 0 commenti 0 reazioni 1 assegnatario Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

@kaovilai ci sta già lavorando.

Dal 23/9/2026.

  • #2473 di @kaovilai — aperta

Valutazione

Questa issue non è ancora stata valutata.

Descrizione

Summary

The 4.22-virt-kdm-e2e-test-aws job failed while checking payload B after a successful incremental CBT backup. ChecksumBlockDeviceRegion received empty stdout from the read-only dd ... | sha256sum pod exec and returned sha256sum produced no output for /dev/volume0 region in alpine-guestagent/virt-launcher-alpine-guestagent-z5796. The same region was checksummed successfully before the backup, and payload A was checksummed successfully immediately before this failure.

This tracks an intermittent E2E checksum-exec failure, not a confirmed backup data-integrity defect or a confirmed API-server stream defect. The reported PR changes only BSL region handling.

Reproduction evidence

  • Job: pull-ci-openshift-oadp-operator-oadp-1.6-4.22-virt-kdm-e2e-test-aws; build ID 2102783124353060864; OCP 4.22.0-0.nightly-2026-09-22-003645.
  • Failed test: restore from an incremental (not full) kubevirt-datamover CBT backup in tests/e2e/virt_backup_restore_suite_test.go (Line 1841).
  • tests/e2e/lib/virt_helpers.go: ChecksumBlockDeviceRegion rejects empty stdout; execShellCommandInPodWithRetry returns immediately when exec returns no error. Its current retry predicate checks for dial tcp errors only.
  • PR: https://github.com/openshift/oadp-operator/pull/2461
  • Original failure analysis: https://github.com/openshift/oadp-operator/pull/2461#issuecomment-5802274985
  • Reported by: @kaovilai

Follow-up

  1. Check the CI artifacts and reruns for recurrence. Capture stdout, stderr, exec errors, and pod status to distinguish a missing exec stream from a command failure.
  2. If an empty successful checksum exec is transient, add a bounded retry for this read-only checksum and a focused test. Keep real command failures visible.
  3. Verify that valid checksums still pass and that persistent empty output still fails with useful diagnostics.

The separately reported kubevirt/kubevirt#18957 SourceLost race is not the checksum failure tracked here. Related E2E exec work: #2451.

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

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.