Aleksei Sviridkin 5b4380dd3b fix(e2e): delete the failed S3 preflight object through a live tunnel ...

The exit trap stopped the port-forward before running mc rm, so the
delete went to a closed port and failed every time, leaving the object
behind and printing a warning that said nothing about why. The delete
now runs first and the warning carries mc's own error, or says the
delete timed out when mc was killed before it could write one.

A PUT that timed out is now also treated as uploaded: it can land and
still outlive its time bound, and the trap never tried to remove such an
object. A PUT the server refused is not, so the common case of access
that never went live does not end in a delete doomed to the same refusal.

Assisted-by: LLM
Signed-off-by: Aleksei Sviridkin <f@lex.la>

2026-10-01 02:10:21 +03:00

..

backup-access-preflight.sh

fix(e2e): delete the failed S3 preflight object through a live tunnel

2026-10-01 02:10:21 +03:00

etcd-cleanup.sh

test(e2e): address review nits — shellcheck directive + ports-workaround TODO

2026-07-10 17:02:46 +05:00

etcd-probe.sh

test(etcd): stop losing the metrics probe's output to the attach race

2026-07-19 20:16:01 +03:00

pod-label-census.sh

fix(e2e): select catch pod logs by the nested release instance label

2026-08-05 16:46:50 +03:00

remediation-guard.sh

test(e2e): pin the release-history read against the upstream type

2026-09-22 23:41:35 +03:00

run-kubernetes.sh

docs(kubernetes): describe the OIDC UID header from v1.33

2026-09-24 15:10:53 +03:00

run-proxmox.sh

test(kubernetes): add the Proxmox e2e suite, parked disabled

2026-09-29 21:04:06 +02:00

talos-image-cache.sh

test(e2e): stop blocking merges on the tenant node-join deadline

2026-08-21 12:52:42 +03:00