action #33868
closed[sle][functional][u]test fails in execute_test_run - setup issue or /usr/share/qa/qa_test_apparmor/wrapper.sh: line 9: ./aa_exec.sh: No such file or directory
0%
Description
Observation¶
openQA test in scenario sle-15-Installer-DVD-s390x-qa_userspace_cracklib@s390x-kvm-sle12 fails in
execute_test_run
Reproducible¶
Fails since (at least) Build 522.1
Expected result¶
Last good: 509.1 (or more recent)
Suggestions¶
- Understand what the test case is doing
- Crosscheck manually
- If necessary reopen bsc#1086254 but only when you can provide better information to the developers where they need to look further
Further details¶
Always latest result in this scenario: latest
Please see reference bug report bsc#1086254.
comment from Kristoffer:
Hi, I have not looked at cracklib before but was asked to have a look at this issue, so forgive me if I'm misunderstanding something that I'm seeing... I find the following in the logs:
Mar 21 06:18:21 susetest passwd[2357]: pam_cracklib(passwd:chauthtok): conversation failed
Mar 21 06:18:21 susetest passwd[2357]: pam_cracklib(passwd:chauthtok): pam_get_authtok_verify returned error: Authentication token manipulation error
Mar 21 06:18:22 susetest passwd[2381]: pam_unix(passwd:chauthtok): authentication failure; logname= uid=1001 euid=0 tty= ruser= rhost= user=testcrypt
"Authentication token manipulation error" is an output from pam_chauthtok:
https://linux.die.net/man/3/pam_chauthtok
PAM_AUTHTOK_ERR, A module was unable to obtain the new authentication token.
Comparing the output of the failing run with the previous successful run, it looks to me like the current password (that was set before running the test) does not match what openqa is passing in:
success:
su testcrypt -c passwd¶
Changing password for testcrypt.
Current password:
New password:
BAD PASSWORD: is too similar to the old one
PASSED: cracklib - similar passwd
failure:
su testcrypt -c passwd¶
Changing password for testcrypt.
Current password:
passwd: Authentication failure
passwd: password unchanged
The new password is never even passed in, so cracklib is presumably never invoked. So it looks like this problem is not really related to cracklib, but the password that was passed to it.
Who would be the appropriate assignee for a problem related to the openQA test itself?`¶
Updated by okurz about 6 years ago
- Subject changed from [sle][functional]test fails in execute_test_run - password is not matching to [sle][functional][u]test fails in execute_test_run - password is not matching
- Description updated (diff)
- Status changed from New to Workable
- Target version set to Milestone 17
Updated by okurz almost 6 years ago
- Target version changed from Milestone 17 to Milestone 21+
Updated by okurz almost 6 years ago
- Target version changed from Milestone 21+ to Milestone 21+
Updated by zluo over 5 years ago
- Status changed from Workable to In Progress
- Assignee set to zluo
take over and try to check this for now:
example for current failure on osd:
http://openqa.suse.de/tests/2248651#step/execute_test_run/45
Updated by zluo over 5 years ago
http://openqa.suse.de/tests/2248651#step/execute_test_run/1 shows that all tests are failed really, atm this problem is not related password. It seems to be product issue to me.
Updated by zluo over 5 years ago
need to verify this, just wondering why no single test got through...
Updated by zluo over 5 years ago
checked execute_test_run-testlog and found:
aa_exec
/usr/share/qa/qa_test_apparmor/wrapper.sh: line 9: ./aa_exec.sh: No such file or directory
So that means we have setup issue before the tests.
Updated by zluo over 5 years ago
- Subject changed from [sle][functional][u]test fails in execute_test_run - password is not matching to [sle][functional][u]test fails in execute_test_run - setup issue or /usr/share/qa/qa_test_apparmor/wrapper.sh: line 9: ./aa_exec.sh: No such file or directory
change the subject.
Updated by yosun over 5 years ago
Seems some tests in apparmor-2.11.0/tests/regression/apparmor/ missing. Solution would be:
- find from upstream https://gitlab.com/apparmor/apparmor/wikis/home/ inside apparmor-2.13.1.tar.gz I can find those test script
- if don't need those sub tests, just remove them from tcf file qa_apparmor-2.11.0.tcf
Updated by yosun over 5 years ago
BTW the script need to update is there https://github.com/SUSE/qa-testsuites/tree/master/tests/qa_test_apparmor
Updated by okurz over 5 years ago
Hi yosun, thanks for trying to help. I am sorry, I have trouble to understand your suggestions, could you try to rephrase please?
Updated by zluo over 5 years ago
checked and compareed apparmor-2.11.0 and apparmor-2.13.1. some test scripts are missing as http://openqa.suse.de/tests/2248651# shows up at end.
To fix this:
use apparmor-2.13.1 to update https://github.com/SUSE/qa-testsuites/tree/master/tests/qa_test_apparmor and make changes in directory tests/regression/apparmor
adapt tcf file
Updated by zluo over 5 years ago
I found also problem with Parser tests because the directory tst and it's content missing. I can try to copy tst from apparmor-2.13.1 to right place.
Updated by zluo over 5 years ago
Updated by yosun over 5 years ago
okurz wrote:
Hi yosun, thanks for trying to help. I am sorry, I have trouble to understand your suggestions, could you try to rephrase please?
The problem is sub-tests missing. To solve it has two solution to choose.
Solution 1. Find the suitable version of test inside https://gitlab.com/apparmor/apparmor/wikis/home/ , and add the missing one into https://github.com/SUSE/qa-testsuites/tree/master/tests/qa_test_apparmor/apparmor-.tar.bz2
The depend on the product you test:
test product < SLE12: 2.5.1
SLE12 < test product < SLE15: 2.8.2
SLE15 < test product: 2.11.0
Solution 2. Just remove those missing sub test from tcf file
https://github.com/SUSE/qa-testsuites/tree/master/tests/qa_test_apparmor/qa_apparmor-.tcf
Updated by yosun over 5 years ago
Sorry, I think I confused you in last email to point out 2.13.1 as an example.
The version of apparmor for test are:
SLE11(XXX): 2.5.1
SLE12(SPX): 2.8.2
SLE15(SPX): 2.11.0
Inside of *.spec file we have define those version. That's why qa_test_apparmor contain different version of tarball.
IMO, the solution could be using upstream test case (inside apparmor-2.11.0.tar.bz2) code to add into the test package already have.
And no need to create a newer one into qa_test_apparamor.
And to test if it work, you could branch code from https://build.suse.de/package/show/QA:Head/qa_test_apparmor , and test if it would works after add those code. (The repo could also find there and available to install it to test).
I suggest to test the build and install for new qa_test_apparmor, since it may bring dependency or conflict after add/modify codes.
Updated by zluo over 5 years ago
PR got updated and merged:
http://e13.suse.de/tests/10049#
However some scripts failed, checking now.
Updated by zluo over 5 years ago
- Status changed from In Progress to Resolved
https://openqa.suse.de/tests/2263889#step/execute_test_run/3 shows the problems which have been reported now:
https://bugzilla.suse.com/show_bug.cgi?id=1116315
The initial problems got resolved and set this ticket as resolved.