Skip to contentSkip to conversation

Test Case "Verify IPMI Root User Password Change" in openbmc-test-automation

DISCUSSION Tony Lee (李文富) 2 participants 4 messages Dec 5, 2019

lore
Share & tools
lore
#0 lore raw

Hi Rahul,

Reference to https://github.com/openbmc/openbmc-test-automation/issues/1920.

Case "Verify IPMI Root User Password Change" will change root user password and unable to reset default password due to the length is limited to 8.
As a result, cases will also fail after this because the password has been changed to 0penBmc1. Should we remove this test case? There seems to be no other way to fix it.

Thanks
Best Regards,
Tony

#1 lore raw

Hi Tony,
We have also faced the same problem. So to avoid such problems, we decided to set BMC password to 8 characters length before running our bucket. As far as skipping such test case, we can do that by using
-e Verify_IPMI_Root_User_Password_Change while running.

Example:
robot -v OPENBMC_HOST:x.x.x.x -e Verify_IPMI_Root_User_Password_Change ipmi/test_ipmi_user.robot

Thanks
Rahul

Quoted 18 lines · Tony Lee (李文富)

Hi Rahul,

Reference to
https://github.com/openbmc/openbmc-test-automation/issues/1920.

Case "Verify IPMI Root User Password Change" will change root user password and
unable to reset default password due to the length is limited to 8. As a result, cases will also fail after this because the password has been changed to 0penBmc1.
Should we remove this test case? There seems to be no other way to fix it.

Thanks
Best Regards,
Tony

#2 lore raw

Hi Rahul,

Got it, it seems I can only skip it first.
There is another question about test_ipmi_user.robot.
Cases which creating a new user success, and then execute a external ipmi command with
this new user account will fail on our system. For example, test case "Verify Setting Valid Password For IPMI User". The key is that the default channel in the Keyword "Set Channel Access" is 1.
"eth0" corresponding to channel 1 is used for debug purposes, and
"eth1" corresponding to channel 2 is used for ipmi remote access in our system.
So once I set the default channel to 2 in the Keyword "Set Channel Access", those cases succeed.

I have a solution: add variable ${CHANNEL} default is 1 in lib/resource.robot. Then, let ${channel}=${CHANNEL} in Keyword "Set Channel Access". Let user to specify channel while running, if not, the default is 1.

Example: robot -v OPENBMC_HOST:x.x.x.x -v CHANNEL:2 ipmi/test_ipmi_user.robot

Is this approach sounds fine to you or there are other suggestions?

Thanks
Tony

From: Rahul Maheshwari <[email protected]>
Sent: Thursday, December 5, 2019 5:47 PM
To: Tony Lee (李文富) <[email protected]>
Cc: [email protected]
Subject: Re: Test Case "Verify IPMI Root User Password Change" in openbmc-test-automation

Hi Tony,
We have also faced the same problem. So to avoid such problems, we decided to set BMC password to 8 characters length before running our bucket. As far as skipping such test case, we can do that by using -e Verify_IPMI_Root_User_Password_Change while running.

Example:
robot -v OPENBMC_HOST:x.x.x.x -e Verify_IPMI_Root_User_Password_Change ipmi/test_ipmi_user.robot

Thanks
Rahul

On Thu, Dec 5, 2019 at 8:05 AM Tony Lee (李文富) <mailto:[email protected]> wrote:
Hi Rahul,

Reference to https://github.com/openbmc/openbmc-test-automation/issues/1920.

Case "Verify IPMI Root User Password Change" will change root user password and unable to reset default password due to the length is limited to 8.
As a result, cases will also fail after this because the password has been changed to 0penBmc1. Should we remove this test case? There seems to be no other way to fix it.

Thanks
Best Regards,
Tony

#3 lore raw

Your solution sound good to me. You can push the code for the same.

Thanks
Rahul

Quoted 68 lines · Tony Lee (李文富)

Hi Rahul,

Got it, it seems I can only skip it first.
There is another question about test_ipmi_user.robot.
Cases which creating a new user success, and then execute a external ipmi command with
this new user account will fail on our system. For example, test case "Verify Setting Valid Password For IPMI User".
The key is that the default channel in the Keyword "Set Channel Access" is 1.
"eth0" corresponding to channel 1 is used for debug purposes, and "eth1" corresponding to channel 2 is used for ipmi remote access in our system.
So once I set the default channel to 2 in the Keyword "Set Channel Access", those cases succeed.

I have a solution: add variable ${CHANNEL} default is 1 in lib/resource.robot.
Then, let ${channel}=${CHANNEL} in Keyword "Set Channel Access". Let user to specify channel while running, if not, the default is 1.

Example: robot -v OPENBMC_HOST:x.x.x.x -v CHANNEL:2 ipmi/test_ipmi_user.robot

Is this approach sounds fine to you or there are other suggestions?

Thanks
Tony

From: Rahul Maheshwari <[email protected]>
Sent: Thursday, December 5, 2019 5:47 PM
To: Tony Lee (李文富) <[email protected]>
Cc: [email protected]
Subject: Re: Test Case "Verify IPMI Root User Password Change" in openbmc-test-automation

Hi Tony,
We have also faced the same problem. So to avoid such problems, we decided to set BMC password to 8 characters length before running our bucket. As far as skipping such test case, we can do that by using
-e Verify_IPMI_Root_User_Password_Change while running.

Example:
robot -v OPENBMC_HOST:x.x.x.x -e Verify_IPMI_Root_User_Password_Change ipmi/test_ipmi_user.robot

Thanks
Rahul

On Thu, Dec 5, 2019 at 8:05 AM Tony Lee (李文富) <mailto:
[email protected]> wrote:
Hi Rahul,

Reference to
https://github.com/openbmc/openbmc-test-automation/issues/1920.

Case "Verify IPMI Root User Password Change" will change root user password and
unable to reset default password due to the length is limited to 8. As a result, cases will also fail after this because the password has been changed to 0penBmc1.
Should we remove this test case? There seems to be no other way to fix it.

Thanks
Best Regards,
Tony