Question about IPMI password MAX length test in openbmc-test-automation

Rahul Maheshwari rahulmaheshwari01 at gmail.com
Tue Jan 7 16:45:21 AEDT 2020


Hi Tony,
I would say option 2 is better. There is no need to verify IPMI command
execution when set user password is expected to fail.

Thanks
Rahul

On Mon, Jan 6, 2020 at 3:06 PM Tony Lee (李文富) <Tony.Lee at quantatw.com> wrote:

> Hi Anusha,
>
> I met an issue that "Verify Setting IPMI User With Invalid Password
> Length" will fail when
> its user id is same as "Verify Setting IPMI User With Max Password Length".
>
> This is because the password length 20 has been successfully set in
> "Verify Setting IPMI User With Max Password Length".
> Therefore, the case of password_length = 21 and password_option = 20 is
> expected to fail but pass when their user id are the same.
>
> I have two solutions:
>
> 1. Only verify the message that cannot use invalid password length to set
> password
> and do not verify that user is able to run IPMI command with given
> username and password in this case.
>
> 2. At the end of each case, delete the user it just created to ensure that
> it will not affect other cases.
>
> Which is better, or do you have other suggestions?
>
> Thanks
> Best Regards,
> Tony
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ozlabs.org/pipermail/openbmc/attachments/20200107/ff4b7f98/attachment.htm>


More information about the openbmc mailing list