Test User Account

[justin0309]

Is this the right place to submit this?

• [X] This is not a security vulnerability or a crashing bug
• [X] This is not a question about how to use OpenBMC
• [X] This is not a bug in an OpenBMC fork or a bug in code still under code review.
• [X] This is not a request for a new feature.

Bug Description

In my Test User Account test in auto-test, there are still three project errors. I have asked auto-test to confirm that it is not a test case issue. https://github.com/openbmc/openbmc-test-automation/issues/2232

Version

code base 2.14.0

Additional Information

No response

[edtanous]

Please provide steps to reproduce, as well as what platform you ran this on.

2.14.0

This version is over a year old; Please attempt to reproduce on a build from master.

[justin0309]

@edtanous But at present, it seems that it has nothing to do with the version,Because I see that the latest version of the code has not been modified in this regard. if I add ec.value()==5, it returns 403. Verify Error While Deleting Root User test item can be passed. Verify SSH Login Access With Admin User and Verify User Account Unlock finally failed to delete user. I can't find the reason for these two test items. As prkatti1 said, it is allowing to create user but not allowing to delete user The test steps are no different, just run redfish/account_service/test_user_account.robot

[edtanous]

Cool, glad you got it figured out.

[justin0309]

@edtanous I think I haven't solved it yet, just like I asked on discord, ec.value()==5, is this 5 equal to Input/output error? Verify SSH Login Access With Admin User Verify User Account Unlock finally failed to delete user. Still haven't passed these two tests. I can't find the reason for these two test items.

[edtanous]

is this 5 equal to Input/output error?

That's a question best answered by the boost system errc docs.

Still haven't passed these two tests.

Considering you're on an old build of a fork, I don't think there's any expectation that those tests pass. If you can reproduce this on a master build of a platform that isn't forked (I generally use S7106 for this kind of thing, because it can run in qemu) and get steps to reproduce that aren't "run the test", we can work through why it's failing; Given that we haven't heard a lot of reports of this test failing, I suspect it was something fixed long ago, but I can't know that until you re-run a test on a master build against a supported platform.

[edtanous]

Closing; No set of steps to reproduce provided (only screenshots of a test run), and is being reported against a year+ old build. Manual testing of this same thing in Redfish service validator shows passing, so unclear where the gap is.

If anything changes, feel free to reopen.