action #30694
closed
[sle][functional][sle12 sp4][sle15][s390x][medium] test fails in reconnect_s390 - passphrase for encrypted disk not typed
Added by zluo over 6 years ago.
Updated about 6 years ago.
Category:
Bugs in existing tests
Description
Observation¶
openQA test in scenario sle-12-SP4-Server-DVD-s390x-lvm-full-encrypt@zkvm fails in
reconnect_s390
Reproducible¶
Fails since (at least) Build 0089
Expected result¶
Last good: SLE 12 SP3 GM
Further details¶
Always latest result in this scenario: latest
- Subject changed from [sle][functional][sle12 sp4] test fails in reconnect_s390 - Correct welcome string not found to [sle][functional][sle12 sp4][medium] test fails in reconnect_s390 - Correct welcome string not found
- Description updated (diff)
- Due date set to 2018-02-13
- Status changed from New to Workable
- Assignee set to okurz
- Target version set to Milestone 14
hm, interesting. I see in the serial output the string "Please enter passphrase for disk cr_vda2!" and the module "boot_encrypt" fails in the wait_serial call trying to find exactly that string. Maybe not in time? first time occurence. Retriggered as https://openqa.suse.de/tests/1415340#live to crosscheck.
The last failed, reproducible, that's good.
- Status changed from Workable to In Progress
- Assignee set to mgriessmeier
I will investigate this - unfortunately there is no autoinst-log.txt anymore for the last good SP3-GM ;(
- Status changed from In Progress to Feedback
so, the problem turned out that we don't extract the SUTs' serial device in this case. Therefore we never actually typed the password in the boot process
Why this was not spotted before:
- for sle12sp3 - we had an explicit call for this, with some refactoring work after SP3 release this was removed
- we only executed this pty extraction on tests which boot an existing image in wait_boot - so related tests worked there
PR created: https://github.com/os-autoinst/os-autoinst-distri-opensuse/pull/4369
verification run: http://opeth/tests/68#step/first_boot/1
- Status changed from Feedback to In Progress
PR needs to be reworked -> in progress again
- Due date changed from 2018-02-13 to 2018-02-27
Moving to the next sprint
- Status changed from In Progress to Blocked
right now, there is no possibility to work on this due to the storage issues on the mainframe - I will revisit this on monday and decide if it can be solved or needs to be moved to the next sprint
- Due date changed from 2018-02-27 to 2018-03-13
- Subject changed from [sle][functional][sle12 sp4][medium] test fails in reconnect_s390 - Correct welcome string not found to [sle][functional][sle12 sp4][medium] test fails in reconnect_s390 - passphrase for encrypted not typed
- Status changed from Blocked to Workable
not blocked anymore, since storage system is back up and running
updated subject line to not confuse it with other tickets which shows similiar behaviour
- Subject changed from [sle][functional][sle12 sp4][medium] test fails in reconnect_s390 - passphrase for encrypted not typed to [sle][functional][sle12 sp4][sle15][s390x][medium] test fails in reconnect_s390 - passphrase for encrypted disk not typed
- Status changed from Workable to In Progress
- Status changed from In Progress to Feedback
- Status changed from Feedback to Resolved
Also available in: Atom
PDF