AES standby to fail if BMC updater services are seen failing

This is to avoid multiple CI code update piplelined failure.

Change-Id: I91db8306583e362ba1265fa1280a8ac83c368955
Signed-off-by: George Keishing <gkeishin@in.ibm.com>
diff --git a/extended/standby_bmc.robot b/extended/standby_bmc.robot
index 0de48e0..9d4df16 100644
--- a/extended/standby_bmc.robot
+++ b/extended/standby_bmc.robot
@@ -17,10 +17,13 @@
 Resource          ../lib/bmc_network_utils.robot
 Resource          ../lib/bmc_cleanup.robot
 Resource          ../lib/dump_utils.robot
+Library           ../lib/gen_misc.py
 
 *** Variables ***
 ${HOST_SETTING}      /org/openbmc/settings/host0
 
+${ERROR_REGEX}  xyz.openbmc_project.Software.BMC.Updater.service: Failed with result 'core-dump'
+
 *** Test Cases ***
 
 Get To Stable State
@@ -69,6 +72,7 @@
 
     Run Keyword And Ignore Error  Delete All Error Logs
     Run Keyword And Ignore Error  Delete All Dumps
+    Check For Application Failures
     Run Keyword And Ignore Error  Remove Journald Logs
 
 *** Keywords ***
@@ -110,6 +114,17 @@
     Check If BMC is Up   5 min    10 sec
 
 
+Check For Application Failures
+    [Documentation]  Parse the journal log and check for failures.
+    [Arguments]  ${error_regex}=${ERROR_REGEX}
+
+    ${error_regex}=  Escape Bash Quotes  ${error_regex}
+    ${journal_log}  ${stderr}  ${rc}=  BMC Execute Command
+    ...  journalctl --no-pager | egrep '${error_regex}'  ignore_err=1
+
+    Should Be Empty  ${journal_log}
+
+
 Validate Parameters
     [Documentation]  Validate PDU parameters.
     Should Not Be Empty   ${PDU_IP}