starlingx
/
test
Code Issues Proposed changes

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 <george.postolache@intel.com>
This commit is contained in:
Lemus Contreras, Cristopher J 2020-03-03 03:07:09 -08:00 committed by George Postolache
parent 70c3583f76
commit b5b362c759
1 changed files with 2 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
automated-robot-suite/Resources/HostManagement.robot
View File

@ -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}