Actions
action #46337
closed[sle][functional][u] test fails in bootloader_zkvm - cannot allocate memory
Start date:
2019-01-17
Due date:
% Done:
0%
Estimated time:
Difficulty:
Description
download of image is successful but yast2 doesn't got started. This issue might be related to #45425
Observation¶
openQA test in scenario sle-15-SP1-Installer-DVD-s390x-create_hdd_pcm_aws@s390x-kvm-sle12 fails in
bootloader_zkvm
Reproducible¶
Fails since (at least) Build 143.1 (current job)
Expected result¶
Last good: 142.1 (or more recent)
Further details¶
Always latest result in this scenario: latest
Updated by mgriessmeier over 5 years ago
- Status changed from New to Feedback
- Assignee set to mgriessmeier
- Priority changed from Normal to Low
the actual issue is here (reading logs helps ;) ):
[2019-01-17T13:10:13.451 CET] [debug] Command executed: virsh define /var/lib/libvirt/images/openQA-SUT-3.xml
[2019-01-17T13:10:13.588 CET] [debug] Command's stderr:
error: Failed to define domain from /var/lib/libvirt/images/openQA-SUT-3.xml
error: cannot fork child process: Cannot allocate memory
Nick and me already took a look - libvirtd process is consuming a lot of memory, it was running for 130 days, we should track this somehow.
but for now - after restarting libvirtd, the memory usage normalized.
keeping on feedback - low, for tracking
Updated by mgriessmeier over 5 years ago
- Subject changed from [sle][functional][u] test fails in bootloader_zkvm - yast2 doesn't start up to [sle][functional][u] test fails in bootloader_zkvm - cannot allocate memory
Updated by okurz over 5 years ago
- Is duplicate of action #45326: [sle][functional][u][s390x[kvm] test fails in bootloader_zkvm - "Cannot allocate memory" when instantiating the virtual machine added
Actions