Files
velero/changelogs/unreleased
Tiger KaovilaiandGitHub 193cfdc58f
Run the E2E test on kind / setup-test-matrix (push) Failing after 3s
e2e-test-kind.yaml / extract (push) Failing after 6s
Run the E2E test on kind / get-go-version (push) Failing after 8s
Run the E2E test on kind / build (push) Skipped
Run the E2E test on kind / run-e2e-test (push) Skipped
push.yml / extract (push) Failing after 6s
Main CI / get-go-version (push) Failing after 8s
Main CI / Build (push) Skipped
Fix datamover backup arg mismatch for CSI CBT service account name (#10318)
* Fix datamover backup arg mismatch for CSI CBT service account name

The exposer built the pod command with --csi-snapshot-metadata-service-sa,
but the datamover backup command only registered --cbt-sa-name. cobra
rejects unknown flags, so the data mover pod exited immediately whenever
a dedicated CBT service account was configured -- and the reverse also
held: since the flags never matched, the SA name never actually reached
the pod, so any code path depending on it stayed unreachable.

Not limited to the block data mover: this line sits outside the
DataMoverTypeVeleroBlock gate and the cbtInfo != nil gate, so it fires
for any CSI snapshot data-movement backup.

Fix: emit --cbt-sa-name (already consumed by the backup command), naming
it consistently with the other CBT flags on the same line (--change-id,
--volume-id, --snapshot-id).

Add a regression test asserting the emitted flag string parses cleanly
against NewBackupCommand's own flag set, so the two sides can't drift
apart again without a test failure.

* Add changelog for #10318

Signed-off-by: Tiger Kaovilai <tkaovila@redhat.com>
2026-09-09 06:34:06 +00:00
..
2026-02-24 23:17:03 +08:00
2026-03-02 10:49:14 +11:00
2026-03-19 02:38:11 +05:30
2026-03-24 20:49:16 +05:30
2026-04-17 15:38:44 +08:00
2026-04-21 14:14:24 +08:00
2026-04-28 03:11:49 -04:00
2026-05-22 06:26:40 +00:00
2026-05-27 14:59:16 +08:00
2026-05-28 14:41:54 +08:00
2026-06-03 13:23:08 +08:00
2026-06-16 17:47:21 +08:00
2026-06-18 15:39:44 +08:00
2026-07-11 10:09:39 +08:00
2026-07-17 16:35:19 +08:00
2026-08-06 10:52:03 +05:30
2026-08-13 12:21:20 -04:00
2026-08-12 22:49:21 +08:00
2026-08-27 12:57:20 -04:00
2026-09-08 18:15:34 +08:00