Removed faillock file check to fix problem
Changes:
- faillock file check is leading to problem. As
it is not a must, removing this check.
Tested:
- Ran below test cases from sandbox successfully
Redfish_Create_and_Verify_Admin_User
Change-Id: I489c3c4bf246cf8a127a74fa2ec3f6e3f6545a8e
Signed-off-by: Rahul Maheshwari <rahulmaheshwari@in.ibm.com>
diff --git a/redfish/account_service/test_user_account.robot b/redfish/account_service/test_user_account.robot
index d45fd3b..5c50698 100644
--- a/redfish/account_service/test_user_account.robot
+++ b/redfish/account_service/test_user_account.robot
@@ -570,7 +570,7 @@
# Resetting faillock count as a workaround for issue
# openbmc/phosphor-user-manager#4
- ${cmd}= Catenate test -f /usr/sbin/faillock && /usr/sbin/faillock --user ${username} --reset
+ ${cmd}= Catenate /usr/sbin/faillock --user ${username} --reset
Bmc Execute Command ${cmd}