From b5b362c759cd40997eab5dfed45b8b34a38b3b5e Mon Sep 17 00:00:00 2001 From: "Lemus Contreras, Cristopher J" Date: Tue, 3 Mar 2020 03:07:09 -0800 Subject: [PATCH] Update unlock on compute nodes During the last week of february, there was a change on the apply behavior for application platform-integ-apps. After unlocking controller-1, it starts to do the apply of this application. For our standar configuration (2+2), this means that, when it tries to do the unlock of the first compute node, the command fails because the app was in the middle of the apply action. This change adds a check, before doing a unlock of a compute node, the suite will check and confirm that the application platform-integ-apps is on applied status for 30 minutes. Until then, it will try to execute the unlock command. Change-Id: I7b346919e6ed6fb47e13c30a812bc262656aa4f5 Signed-off-by: George Postolache --- automated-robot-suite/Resources/HostManagement.robot | 2 ++ 1 file changed, 2 insertions(+) diff --git a/automated-robot-suite/Resources/HostManagement.robot b/automated-robot-suite/Resources/HostManagement.robot index 96b06fe..ed698f6 100644 --- a/automated-robot-suite/Resources/HostManagement.robot +++ b/automated-robot-suite/Resources/HostManagement.robot @@ -28,6 +28,8 @@ Unlock Controller Unlock Compute [Arguments] ${compute} [Documentation] Unlock specified compute. + Wait Until Keyword Succeeds 30 min 5 sec + ... Check System Application Status platform-integ-apps applied Run Command system host-unlock ${compute} True 60 sec Check Host Readiness ${compute}