Commit 5f94035
test(e2e): drop csi-pvc-local — storage-only auto-mkfs needs follow-up
Live validation on the piraeus interop lane showed csi-pvc-local
hanging at PVC=Pending: linstor-csi created the RD/VD/placement, then
csi-provisioner timed out and DeleteVolume'd the slot in a loop.
The DRBD-replicated test (csi-pvc-replicated-rwo) PASSed cleanly,
confirming the DRBD auto-mkfs path works end-to-end against linstor-csi
through blockstor's apiserver.
The storage-only auto-mkfs commit (8b48347) was reverted in the
preceding commit because the runStorageOnlyMkfs hook never reached
PVC=Bound on the live stand even though all 14 TestApplyAutoMkfs*
unit tests stayed green. The shape of the wedge points at the
linstor-csi placement → satellite handshake (no fsck error surfaced
on the node side — Pod stayed at FailedMount "PVC is not bound").
Needs a focused investigation against the actual linstor-csi v1.10.1
NodePublishVolume flow before re-introducing.
Drop the failing scenario and pin only the working DRBD path so PR
#35 lands clean as workflow+test infrastructure. Storage-only PVC
support tracked as follow-up.
Co-Authored-By: Claude <noreply@anthropic.com>
Signed-off-by: Andrei Kvapil <kvapss@gmail.com>1 parent 218d94c commit 5f94035
2 files changed
Lines changed: 2 additions & 267 deletions
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
239 | 239 | | |
240 | 240 | | |
241 | 241 | | |
242 | | - | |
| 242 | + | |
243 | 243 | | |
244 | 244 | | |
245 | 245 | | |
| |||
366 | 366 | | |
367 | 367 | | |
368 | 368 | | |
369 | | - | |
| 369 | + | |
370 | 370 | | |
371 | 371 | | |
372 | 372 | | |
| |||
This file was deleted.
0 commit comments