-
Notifications
You must be signed in to change notification settings - Fork 75
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
testAddDiskNFS troubleshooting #1909
Conversation
Ah! The only thing that shows me something is our automatically captured console log:
and then it auto-reboots. That is with the cockpit-project/bots#7095 image with the temporary kernel build. But it happens the same way with 6.11.0-29.el10.x86_64 on centos-10 (we just don't regularly test c-machines on our own centos-10 image):
I also confirmed it with our current centos-10 image with 6.11.0-27.el10.x86_64 Reported as https://issues.redhat.com/browse/RHEL-67841 |
4745282
to
51ecaf5
Compare
I am running out of ideas. I skipped the test now on RHEL 10, which ought to fix the c10s TF run as well. |
NFS produces dozens of permissive=1 SELinux issues; setroubleshoot runs massively parallel on them, and eats up too much RAM and I/O. Avoid this by disabling setroubleshootd for this test. https://bugzilla.redhat.com/show_bug.cgi?id=2326499
RHEL 10 got a nasty kernel oops [1] which unceremoniously reboots the VM without leaving any journal trace, only the QEMU console shows it. It completely breaks Testing Farm runs (it cannot recover from reboots) and also breaks our own CI in nasty ways, as after the reboot the nondestructive recovery fails in all kinds of ways. Fixes cockpit-project#1900 [1] https://issues.redhat.com/browse/RHEL-67841
51ecaf5
to
ea28d9e
Compare
This fixes cockpit-project/bots#7095
Fixes #1900.