action #75331
Updated by riafarov over 3 years ago
See #75178. Not to lose coverage, we should cover testing of the basic functionality in our job group, like we did for other test modules. Currently yast2 kdump module is used for test configuration in kdump and crash: https://openqa.suse.de/tests/latest?arch=ppc64le&distri=sle&flavor=Online&machine=ppc64le-spvm&test=extra_tests_fadump_lvm_encrypt&version=15-SP3 We should implement new test module which does kdump configuration using yast, but do not cover kernel crash. For this scenario we can skip testing kdump itself as will be covered by kernel team, whereas we need to validate configuration part. Module might have some dependencies, which we will have to provide in the test suite where we kdump testing is out of scope ## Acceptance criteria 1. kdump yast module is tested on the same backends as currently is in kernel job group 2. Configuration is validated either indirectly by crashing the kernel, as is, or is improved by checking the configuration directly