Chris Peterson has proposed merging ~cpete/ubuntu-manual-tests:kernel-crash-dumps-automatic-enablement-test into ubuntu-manual-tests:main.
Requested reviews: Ubuntu Testcase Admins (ubuntu-testcase) For more details, see: https://code.launchpad.net/~cpete/ubuntu-manual-tests/+git/ubuntu-manual-tests/+merge/473601 Add new test cases for checking automatic enable and disable of kernel crash dumps in the installer images using kdump-tools. The test cases are slightly generic with the intention of adding them as: - Required tests in the amd64 tests of the "Ubuntu" product - Required tests in the amd64 tests of the "Ubuntu Server Subiquity" product - (Disabled test only) An optional test in the riscv tests of the "Ubuntu Server Subiquity" product -- Your team Ubuntu Testcase Admins is requested to review the proposed merge of ~cpete/ubuntu-manual-tests:kernel-crash-dumps-automatic-enablement-test into ubuntu-manual-tests:main.
diff --git a/testcases/image/1822_Install Kernel Crash Dumps Automatic (Enabled) b/testcases/image/1822_Install Kernel Crash Dumps Automatic (Enabled) new file mode 100644 index 0000000..5ce2441 --- /dev/null +++ b/testcases/image/1822_Install Kernel Crash Dumps Automatic (Enabled) @@ -0,0 +1,93 @@ +<p> +The purpose of this testcase is to test that kernel crash dumps are +<b>successfully enabled</b> on installed systems which meet certain criteria. +The result of this test case will depend on the specifics of your hardware. +Please perform the test using a system that <b>meets</b> the following minimum +criteria: +</p> + +<table> + <tr> + <th>Hardware items</th> + <th> Minimum specification</th> + </tr> + <tr> + <td>CPU Architecture</td> + <td> amd64 (x86_64), arm64 (aarch64), or s390x</td> + </tr> + <tr> + <td>CPU Cores</td> + <td> >=4</td> + </tr> + <tr> + <td>Memory (RAM + SWAP)</td> + <td> >=6GiB</td> + </tr> + <tr> + <td>Disk space in /var</td> + <td> 5 x (Memory)</td> + </tr> +</table> + +<em> + Proceed in your native language if you wish. Instructions will remain in + English. +</em> + +<p> The test steps are as follows: </p> + +<ol> + <li> Perform a standard install using the linked installation media, ensuring + the drive <code>/var</code> is mounted to has sufficient free space. + No other special steps are required during the installation. </li> + <li> Reboot into the newly installed system. </li> + <li> Check on the status of kdump-tools using the following command: <code>kdump-config show</code></li> + <li> Compare the result of the command with the guidance below. </li> +</ol> + +<p> The result of the <code>kdump-config show</code> command should show +something similar to:</p> +<div class="box"> + <pre> + $ kdump-config show + DUMP_MODE: kdump + USE_KDUMP: 1 + KDUMP_COREDIR: /var/crash + crashkernel addr: 0x + /var/lib/kdump/vmlinuz: symbolic link to /boot/vmlinuz-6.11.0-7-generic + kdump initrd: + /var/lib/kdump/initrd.img: symbolic link to /var/lib/kdump/initrd.img-6.11.0-7-generic + current state: ready to kdump + + crashkernel suggested size: 223M + + kexec command: + /sbin/kexec -p --command-line="BOOT_IMAGE=/boot/vmlinuz-6.11.0-7-generic root=UUID=8c19e778-298a-40ad-91cd-f6725092446a ro reset_devices systemd.unit=kdump-tools-dump.service nr_cpus=1 irqpoll usbcore.nousb" --initrd=/var/lib/kdump/initrd.img /var/lib/kdump/vmlinuz + </pre> +</div> + +<p> Ensure that: </p> +<ul> + <li><b>current state</b> shows <b> ready to dump</b>.</li> + <li> USE_KDUMP is set to <b>1</b></li> + <li> The <i>crashkernel</i> parameter is set on the kernel command line. + (this can be checked using: <code>sudo cat /proc/cmdline)</code></li> +</ul> + + +<strong> Some special notes about testing: </strong> +<ul> + <li> If the results are not as expected, please include the output of the + following command in your bug report: + <code>sudo /usr/share/kdump-tools/kdump_set_default</code> + </li> + <li> If performing the test with a VM, note that it has been reported that + thin provisioning of disk images may cause the enablement to fail + where it was otherwise expected. Check the output of + <code>df -h /var</code> within the VM in these cases. + </li> +</ul> + +<strong>If you finish the installation, please <a href="results#add_result">submit</a> a 'passed' result. + If any action fails, or produces an unexpected result, please <a href="results#add_result">submit</a> a 'failed' result and <a href="../../buginstructions">file a bug</a>. Please be sure to include the bug number when you <a href="results#add_result">submit</a> your result.</strong> + diff --git a/testcases/image/1823_Install Kernel Crash Dumps Automatic (Disabled) b/testcases/image/1823_Install Kernel Crash Dumps Automatic (Disabled) new file mode 100644 index 0000000..8faecd3 --- /dev/null +++ b/testcases/image/1823_Install Kernel Crash Dumps Automatic (Disabled) @@ -0,0 +1,87 @@ +<p> +The purpose of this testcase is to test that kernel crash dumps are +<b>successfully disabled</b> on installed systems which do not meet certain criteria. +The result of this test case will depend on the specifics of your hardware. +Please perform the test using a system that <b>does not meet</b> the following +minimum criteria: +</p> + +<table> + <tr> + <th>Hardware items</th> + <th> Minimum specification</th> + </tr> + <tr> + <td>CPU Architecture</td> + <td> amd64 (x86_64), arm64 (aarch64), or s390x</td> + </tr> + <tr> + <td>CPU Cores</td> + <td> >=4</td> + </tr> + <tr> + <td>Memory (RAM + SWAP)</td> + <td> >=6GiB</td> + </tr> + <tr> + <td>Disk space in /var</td> + <td> 5 x (Memory)</td> + </tr> +</table> + +<em> + Proceed in your native language if you wish. Instructions will remain in + English. +</em> + +<p> The test steps are as follows: </p> + +<ol> + <li> Perform a standard install using the linked installation media. + No other special steps are required during the installation. </li> + <li> Reboot into the newly installed system. </li> + <li> Check on the status of kdump-tools using the following command: <code>kdump-config show</code></li> + <li> Compare the result of the command with the guidance below. </li> +</ol> + + +<p> The result of the <code>kdump-config show</code> command should show +something similar to:</p> +<div class="box"> + <pre> + $ kdump-config show + * /etc/default/kdump-tools: USE_KDUMP is not set or zero + DUMP_MODE: kdump + USE_KDUMP: 0 + KDUMP_COREDIR: /var/crash + crashkernel addr: 0x + /var/lib/kdump/vmlinuz: symbolic link to /boot/vmlinuz-6.11.0-7-generic + kdump initrd: + /var/lib/kdump/initrd.img: symbolic link to /var/lib/kdump/initrd.img-6.11.0-7-generic + current state: Not ready to kdump + + crashkernel suggested size: 215M + + kexec command: + /sbin/kexec -p --command-line="BOOT_IMAGE=/boot/vmlinuz-6.11.0-7-generic root=UUID=8c19e778-298a-40ad-91cd-f6725092446a ro reset_devices systemd.unit=kdump-tools-dump.service nr_cpus=1 irqpoll usbcore.nousb" --initrd=/var/lib/kdump/initrd.img /var/lib/kdump/vmlinuz + </pre> +</div> + +<p> Ensure that: </p> +<ul> + <li><b>current state</b> shows <b>Not ready to dump</b>.</li> + <li> USE_KDUMP is set to <b>0</b></li> +</ul> + + +<strong> Some special notes about testing: </strong> +<ul> + <li> If the results are not as expected, please include the output of the + following command in your bug report: + <code>sudo /usr/share/kdump-tools/kdump_set_default</code> + </li> +</ul> + +<strong>If you finish the installation, please <a href="results#add_result">submit</a> a 'passed' result. + If any action fails, or produces an unexpected result, please <a href="results#add_result">submit</a> a 'failed' result and <a href="../../buginstructions">file a bug</a>. Please be sure to include the bug number when you <a href="results#add_result">submit</a> your result.</strong> +
-- Mailing list: https://launchpad.net/~kubuntu-council Post to : kubuntu-council@lists.launchpad.net Unsubscribe : https://launchpad.net/~kubuntu-council More help : https://help.launchpad.net/ListHelp
