-
Notifications
You must be signed in to change notification settings - Fork 33
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
mkdumprd: failed to make kdump initrd after enabling kdump #6114
Comments
The underlying reason is that `systemctl start kdump` fails because rebuilding the initrd fails (without any useful error). That manifests differently in our three tests, so add three patterns. Downstream report: https://bugzilla.redhat.com/show_bug.cgi?id=2270423 Known issue #6114
fedora-40
First occurrence: 2024-03-20T12:59:14.697632 | revision 5ce7524
|
fedora-40
First occurrence: 2024-06-07T16:24:03.503746+00:00 | revision 984038f39d1c82f69f2a890d987ca83cfb071509
First occurrence: 2024-06-07T16:42:06.280089+00:00 | revision 984038f39d1c82f69f2a890d987ca83cfb071509
First occurrence: 2024-06-07T16:44:55.819094+00:00 | revision 984038f39d1c82f69f2a890d987ca83cfb071509
|
The underlying reason is that `systemctl start kdump` fails because rebuilding the initrd fails (without any useful error). That manifests differently in our three tests, so add three patterns. Downstream report: https://bugzilla.redhat.com/show_bug.cgi?id=2270423 Known issue #6114
The underlying reason is that `systemctl start kdump` fails because rebuilding the initrd fails (without any useful error). That manifests differently in our three tests, so add three patterns. Downstream report: https://bugzilla.redhat.com/show_bug.cgi?id=2270423 Known issue #6114
The underlying reason is that `systemctl start kdump` fails because rebuilding the initrd fails (without any useful error). That manifests differently in our three tests, so add three patterns. Downstream report: https://bugzilla.redhat.com/show_bug.cgi?id=2270423 Known issue #6114
Downstream report: https://bugzilla.redhat.com/show_bug.cgi?id=2270423
The text was updated successfully, but these errors were encountered: