Fix for BMC dump persistence test case
Changes:
- Added Host power off so that the dump is not offloaded to host OS.
Tested:
- Executed dump persistence test case from sandbox successfully.
Signed-off-by: manashsarma <manashsarma@in.ibm.com>
Change-Id: I10bea067d1cd10bdfa02afe762cbd5df652b3e80
diff --git a/redfish/managers/test_bmc_dumps.robot b/redfish/managers/test_bmc_dumps.robot
index 1d7a4e5..416c690 100644
--- a/redfish/managers/test_bmc_dumps.robot
+++ b/redfish/managers/test_bmc_dumps.robot
@@ -87,6 +87,9 @@
[Documentation] Create user dump, reset BMC and verify dump persistency.
[Tags] Verify_Dump_Persistency_On_BMC_Reset
+ # Power off host so that dump is not offloaded to host OS.
+ Redfish Power Off stack_mode=skip
+
Create User Initiated BMC Dump Via Redfish
${dump_entries_before}= redfish_utils.get_member_list /redfish/v1/Managers/bmc/LogServices/Dump/Entries