From fc07d30f2cbe58e088c0df4bb32721ce061dba79 Mon Sep 17 00:00:00 2001 From: Chris Date: Tue, 6 Feb 2024 16:10:28 +0800 Subject: [PATCH] Add skeleton for test_engine_crash_during_live_upgrade ref: 7859 Signed-off-by: Chris --- manager/integration/tests/test_engine_upgrade.py | 16 ++++++++++++++++ 1 file changed, 16 insertions(+) diff --git a/manager/integration/tests/test_engine_upgrade.py b/manager/integration/tests/test_engine_upgrade.py index 2c16d6a8c1..cc97b64d12 100644 --- a/manager/integration/tests/test_engine_upgrade.py +++ b/manager/integration/tests/test_engine_upgrade.py @@ -1196,3 +1196,19 @@ def test_engine_live_upgrade_while_replica_concurrent_rebuild(client, # NOQA for replica in volume2.replicas: assert replica.image == engine_upgrade_image assert replica.currentImage == engine_upgrade_image + +@pytest.mark.skip(reason="TODO") # NOQA +def test_engine_crash_during_live_upgrade(): + """ + 1. Create and attach a volume to a workload, then write data into the + volume. + 2. Deploy an extra engine image. + 3. Send live upgrade request then immediately delete the related engine + manager pod/engine process (The new replicas are not in active in this + case). + 4. Verify the workload will be restarted and the volume will be reattached + automatically. + 5. Verify the upgrade is done during the reattachment. + (It actually becomes offline upgrade.) + 6. Verify volume healthy and the data is correct. + """