action #177507
open[qe-core] random_write_wakeup_threshold has unexpected value
100%
Description
Observation¶
This is happening randomly on 15-SP5 only AFAIK
No idea what is causing this, but when the parent job is restarted the value is correct.
Would be good to find out what is causing this random change and fix it or workaround this issue.
openQA test in scenario sle-15-SP5-Server-DVD-Incidents-x86_64-mau-sles-sys-param-check@64bit-2gbram fails in
Sysctl
Test suite description¶
https://gitlab.suse.de/qa-css/sys-param-check
Reproducible¶
Fails since (at least) Build :36971:maven-doxia
Expected result¶
Last good: :37508:openssh (or more recent)
Further details¶
Always latest result in this scenario: latest
Updated by rfan1 10 days ago
I am not sure if something different with worker worker34, but seems if parent job runs on this server, we can get new sysctl value on child test,
I can reproduce it as well http://openqa.suse.de/tests/overview?distri=sle&version=15-SP5&build=rfan0211
Maybe it is the same issue mentioned in bug https://bugzilla.suse.com/show_bug.cgi?id=1198251.
I don't know if any special setting on this worker.
Updated by dzedro 10 days ago
rfan1 wrote in #note-1:
I am not sure if something different with worker
worker34, but seems if parent job runs on this server, we can get new sysctl value on child test,I can reproduce it as well http://openqa.suse.de/tests/overview?distri=sle&version=15-SP5&build=rfan0211
Maybe it is the same issue mentioned in bug https://bugzilla.suse.com/show_bug.cgi?id=1198251.
I don't know if any special setting on this worker.
Yes, that's probably it, I guess we can just add QEMU_VIRTIO_RNG=0