From 49d59f310ecf233f47128aa7da814c5ee4a6e35c Mon Sep 17 00:00:00 2001 From: Jon Cope Date: Wed, 1 Apr 2026 16:49:07 -0500 Subject: [PATCH] Fix bug: fix certificate rotation test time mismatch The certificate rotation test changes system time on the remote MicroShift host, but Wait For MicroShift runs oc commands locally on the test runner where time hasn't changed. This causes TLS validation to fail because regenerated certificates have NotBefore set to the future time. Use Wait For MicroShift Healthcheck Success instead, which runs via SSH on the remote host using the manipulated time. Co-Authored-By: Claude Opus 4.5 --- test/suites/standard2/validate-certificate-rotation.robot | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/test/suites/standard2/validate-certificate-rotation.robot b/test/suites/standard2/validate-certificate-rotation.robot index 64bcfc274f..37411708e7 100644 --- a/test/suites/standard2/validate-certificate-rotation.robot +++ b/test/suites/standard2/validate-certificate-rotation.robot @@ -64,7 +64,7 @@ Change System Date To Wait Until MicroShift Process ID Changes ${ushift_pid} All Certificates Should Be Valid For Current Time Setup Kubeconfig - Wait For MicroShift + Restart Greenboot And Wait For Success Compute Date After Days [Documentation] return system date after number of days elapsed