action #34930
closed[sle][functional][u] test fails in start_install
0%
Description
x86_64 https://openqa.suse.de/tests/1589137#previous or PPC https://openqa.suse.de/tests/1589144#previous do not encounter the same issue.
Although aarch64 fails often on creating logical volume, it is not really clear whether we are dealing with product bug or test issue.
Creating logical volume /dev/system/root
LVM_LV_CREATE_FAILED
System error code was: -4014
/sbin/lvcreate -A n --zero=y --yes -l 2048 --name 'root' 'system':
/run/lvm/lvmetad.socket: connect failed: No such file or directory
WARNING: Failed to connect to lvmetad. Falling back to internal scanning.
WARNING: This metadata update is NOT backed up
device-mapper: reload ioctl on (252:1) failed: No such device or address
Observation¶
openQA test in scenario sle-12-SP4-Server-DVD-aarch64-cryptlvm@aarch64 fails in
start_install
Reproducible¶
Fails since (at least) Build 0235
Expected result¶
Last good: 0234 (or more recent)
Further details¶
Always latest result in this scenario: latest
Updated by okurz almost 6 years ago
- Subject changed from [sle][functional] test fails in start_install to [sle][functional][u] test fails in start_install
- Due date set to 2018-06-19
- Target version set to Milestone 17
Updated by okurz almost 6 years ago
- Status changed from New to Rejected
- Assignee set to okurz
I don't see any indication where the test is doing something wrong. What should we do differently? However, that problem seems to have appeared only once or at least limited times and is fine again in more recent jobs, e.g. build 0238 : https://openqa.suse.de/tests/1667881 so I guess we can just accept it as is.
Updated by okurz almost 6 years ago
- Target version changed from Milestone 17 to Milestone 17