E2E common CI test#289
Conversation
E2E tests ❌Module: sds-node-configurator
JUnit is published in run-tests job checks. |
E2E tests ❌Module: sds-node-configurator
JUnit is in Checks (run-tests job). |
2 similar comments
E2E tests ❌Module: sds-node-configurator
JUnit is in Checks (run-tests job). |
E2E tests ❌Module: sds-node-configurator
JUnit is in Checks (run-tests job). |
E2E tests ❌Module: sds-node-configurator
JUnit is in Checks (run-tests job). |
1 similar comment
E2E tests ❌Module: sds-node-configurator
JUnit is in Checks (run-tests job). |
E2E tests ❌Module: sds-node-configurator
JUnit is in Checks (run-tests job). |
1 similar comment
E2E tests ❌Module: sds-node-configurator
JUnit is in Checks (run-tests job). |
E2E tests ❌Module: sds-node-configurator
JUnit is in Checks (run-tests job). |
E2E tests ❌Module: sds-node-configurator
JUnit is in Checks (run-tests job). |
1 similar comment
E2E tests ❌Module: sds-node-configurator
JUnit is in Checks (run-tests job). |
Avoid attaching VirtualDisks to orphan VMs in the PR namespace; BlockDevice discovery only runs on nodes where sds-node-configurator agent is scheduled. Co-authored-by: Cursor <cursoragent@cursor.com>
E2E tests ❌Module: sds-node-configurator
JUnit is in Checks (run-tests job). |
1 similar comment
E2E tests ❌Module: sds-node-configurator
JUnit is in Checks (run-tests job). |
E2E tests ❌Module: sds-node-configurator
JUnit is in Checks (run-tests job). |
1 similar comment
E2E tests ❌Module: sds-node-configurator
JUnit is in Checks (run-tests job). |
E2E tests ✅Module: sds-node-configurator
JUnit is in Checks (run-tests job). |
E2E tests ❌Module: sds-node-configurator
JUnit is in Checks (run-tests job). |
3 similar comments
E2E tests ❌Module: sds-node-configurator
JUnit is in Checks (run-tests job). |
E2E tests ❌Module: sds-node-configurator
JUnit is in Checks (run-tests job). |
E2E tests ❌Module: sds-node-configurator
JUnit is in Checks (run-tests job). |
E2E tests ❌Module: sds-node-configurator
JUnit is in Checks (run-tests job). |
2 similar comments
E2E tests ❌Module: sds-node-configurator
JUnit is in Checks (run-tests job). |
E2E tests ❌Module: sds-node-configurator
JUnit is in Checks (run-tests job). |
E2E tests ❌Module: sds-node-configurator
JUnit is in Checks (run-tests job). |
2 similar comments
E2E tests ❌Module: sds-node-configurator
JUnit is in Checks (run-tests job). |
E2E tests ❌Module: sds-node-configurator
JUnit is in Checks (run-tests job). |
Signed-off-by: Nikolay Demchuk nikolay.demchuk@flant.com
Description
Move e2e out of
build_devinto a dedicatede2e-test.ymlworkflow on the storage-e2e reusable pipeline (triggered by thee2e-testlabel), add a scenario for controller pod restart preserving managed VG/BD state, introduce a shared base-cluster SSH connect helper, and updateE2E_USAGE.md/README.md.Why do we need it, and what problem does it solve?
E2e should run separately from build/trivy on demand, and we need automated coverage that after an
sds-node-configuratorpod restart managedLVMVolumeGroupandBlockDeviceobjects are not recreated and reconcile back toReady.What is the expected result?
A PR labeled
e2e-testruns the E2E tests workflow (create-cluster → run-tests → teardown-cluster), publishes JUnit in checks and a result comment on the PR, removes the label when done, leaves Build and checks without e2e, and the new test passes with unchanged BD/LVG UIDs after the controller pod restart.Checklist