Merge ~fheimes/ubuntu-manual-tests/+git/ubuntu-manual-tests:master into ubuntu-manual-tests:master

[Frank Heimes]

[Paride Legovini (paride)]

LGTM

review: Approve

diff --git a/testcases/image/1728_PPC64EL Install using Netboot (Petitboot) b/testcases/image/1728_PPC64EL Install using Netboot (Petitboot)
new file mode 100644
index 0000000..7b71ae5
--- /dev/null
+++ b/testcases/image/1728_PPC64EL Install using Netboot (Petitboot)
@@ -0,0 +1,33 @@
+This testcase is to be carried out on an IBM POWER system (POWER 8 or higher, but cannot be executed on a PowerVM DLPAR). 
+Scope of this testcase is to verify that the system can be installed using a live server image and netbooting from the Petitboot firmware prompt.
+
+<em>Proceed in your native language if you wish. Instructions will remain in English.</em>
+
+<dl>
+    <dt>Boot up a system using IPMI, monitor the (sol) console, until the Petitboot menu shows up and select 'Exit to shell'.</dt>
+        <dd>It takes takes a while to boot the OPAL firmware aka embedded Linux up to the Petitboot menu.</dd>
+        <dd>Select 'Exit to shell' in Petitboot promptly before the system times out and proceeds with booting from the default device.</dd>
+    <dt>Download the ISO image, usually the one mentioned here in the QA tracker that was requested to be tested, using wget (a proxy server might need to be specified).</dt>
+        <dd>wget http://path/to/image.iso   # proxy might be needed: '-e use_proxy=yes -e http_proxy=squid.internal:3128' </dd>
+    <dt>Loop-back mount the ISO image:</dt>
+        <dd>mkdir iso</dd>
+        <dd>mount -t iso9660 -o loop image.iso iso</dd>
+    <dt>Start The installer using kexec</dt>
+        <dd>kexec -l ./iso/casper/vmlinux --initrd=./iso/casper/initrd.gz --append="ip=dhcp url=http://path/to/image.iso --- quiet"</dd>
+        <dd>kexec -e</dd>
+    <dt>The subiquity UI will pop-up after some time, choose your desired language, or confirm the default 'English'.</dt>
+    <dt>At the network configuration screen, just select 'Done' (it should be pre-selected).</dt>
+    <dt>At the filesystem setup screen, select "Use An Entire Disk" (should be pre-selected).</dt>
+    <dt>Choose a disk to install to.</dt>
+    <dt>At the file system summary screen select Done (should be selected by default).</dt>
+    <dt>At the confirmation dialog, select "Continue" (should not be selected by default).</dt>
+    <dt>Fill out the user information dialog, ideally making sure to import your SSH keys from git or launchpad.</dt>
+    <dt>Wait until the installation is completed.</dt>
+    <dt>Reboot the system, and monitor the progress via the (sol) console.</dt>
+    <dt>Ensure that it's possible to login to the system.</dt>
+    <dt>Ensure that you can run commands with sudo.</dt>
+    <dt>Check that the correct SSH keys have been imported by SSHing into the machine or looking in ~/.ssh./</dt>
+</dl>
+<strong>If all actions produce the expected results listed, please <a href="results#add_result">submit</a> a 'passed' result.
+    If an 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/1729_S390X Install LPAR (Server live) b/testcases/image/1729_S390X Install LPAR (Server live)
new file mode 100644
index 0000000..3917885
--- /dev/null
+++ b/testcases/image/1729_S390X Install LPAR (Server live)
@@ -0,0 +1,34 @@
+This testcase is to be carried out on an IBM Z logical partition (LPAR). (Notice that the minimal architectural requirement is z13/z13s, starting with Ubuntu Server 20.04, otherwise zEC12/zBC12.)
+Scope of this testcase is to verify that an Ubuntu Server live image can be installed on LPAR with the help of the HMC.
+
+<em>Proceed in your native language if you wish. Instructions will remain in English.</em>
+
+<dl>
+    <dt>Download the live server ISO image to your install server, loopback-mount (or better extract) it there and make it remotely available via ftp.</dt>
+    <dt>Boot up a live server image with the help of the 'Load from Removable Media and Server' task of the HMC (Hardware Management Console).</dt>
+    <dt>If the basic network configuration was not specified in the parmfile, the installer will interactively ask about it.</dt>
+        <dd>Start the interactive questionnaire about the basic network configuration and make sure that the URL to image, that needs to be specified too, is accessible (hence, ideally point to the image located on the install server).</dd>
+    <dt>If the boot-up of the installation system is complete, open the "Integrated ASCII Console" or use a remote ssh installer session (recommended) to connect to the live installer.</dt>
+        <dd>A temporary installation password can be found at the end of the ('Operating System Messages') console boot log, like:</dd>
+        <dd>|37.487176| cloud-init¬1873|: installer:BpAGSH2HAMY5testcbvZ</dd>
+    <dt>The subiquity UI will be displayed after login - choose your desired language, or confirm the default 'English'.</dt>
+    <dt>At the 'Zdev setup' screen select zfcp-host devices (usually two) and enable them (make sure the correct devices for your particular LPAR are used.</dt>
+        <dd>Now all available (usually four) paths must be automatically detected (multipath).</dd>
+        <dd>Alternatively DASD disk storage can be selected - if available.</dd>
+        <dd>Overall it's recommended that zFCP/SCSI, as well as DASD disk storage, is tested. Hence if a second LPAR installation is done, it's recommended to use DASD instead of zFCP/SCSI disk storage that time.</dd>
+    <dt>At the network configuration screen, select 'Done' (it should be pre-selected).</dt>
+    <dt>At the filesystem setup screen, select "Use An Entire Disk" (should be pre-selected).</dt>
+    <dt>Choose a disk to install to.</dt>
+    <dt>At the file system summary screen select 'Done' (should be pre-selected).</dt>
+    <dt>At the confirmation dialog, select 'Continue'.</dt>
+    <dt>Fill out the user information dialog, ideally including the import of your SSH keys from launchpad (or github).</dt>
+    <dt>Wait until the installation is complete and select 'Reboot'.</dt>
+    <dt>You may optionally monitor the (re-)boot progress via the console ('Operating System Messages' HMC task).</dt>
+    <dt>Ensure that it's possible to login to the system.</dt>
+    <dt>Ensure that you can run commands with sudo (like for example 'sudo apt update').</dt>
+    <dt>Ensure that the correct s390x devices were configured (like for example with 'lszdev --online').</dt>
+    <dt>Check that the correct SSH keys have been imported by SSHing into the machine or looking at ~/.ssh .</dt>
+</dl>
+<strong>If all actions produce the expected results listed, please <a href="results#add_result">submit</a> a 'passed' result.
+    If an 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/1730_S390X Install zVM (Server live) b/testcases/image/1730_S390X Install zVM (Server live)
new file mode 100644
index 0000000..018c660
--- /dev/null
+++ b/testcases/image/1730_S390X Install zVM (Server live)
@@ -0,0 +1,35 @@
+This testcase is to be carried out on an IBM z/VM guest (virtual machine). (Notice that the minimal architectural requirement is z13/z13s, starting with Ubuntu Server 20.04, otherwise zEC12/zBC12.)
+Scope of this testcase is to verify that an Ubuntu Server live image can be installed on an IBM z/VM guest with the help of a 3270 terminal emulator.
+
+<em>Proceed in your native language if you wish. Instructions will remain in English.</em>
+
+<dl>
+    <dt>Download the live server ISO image to your install server, loopback-mount (or better extract) it there and make it remotely available via ftp.</dt>
+    <dt>Connect the z/VM guest that is going to be installed with the help of a 3270 terminal emulator (usually x3270 or c3270).</dt>
+    <dt>Transfer the kernel, initrd, parmfile and REXX script, located in the boot folder of the ISO image, to the z/VM guest (either with ftp or with the help of the 3270 terminal emulator file transfer functionality.</dt>
+    <dt>Boot up a live server image by executing the ubuntu REXX script from CMS running inside of the z/VM guest.</dt>
+    <dt>If the basic network configuration was not specified in the parmfile, the installer will interactively ask about it.</dt>
+        <dd>Start the interactive questionnaire about the basic network configuration and make sure the URL to image (that needs to be specified in addition) is accessible (hence, ideally point to the image located on the install server.)</dd>
+    <dt>If the boot-up of the installation system is complete, use a remote ssh installer session to connect to the live installer.</dt>
+        <dd>A temporary installation password can be found at the end of the (3270) console boot log, like:</dd>
+        <dd>|37.487176| cloud-init¬1873|: installer:BpAGSH2HAMY5testcbvZ</dd>
+    <dt>The subiquity UI will be displayed after login - choose your desired language, or confirm the default 'English'.</dt>
+    <dt>At the 'Zdev setup' screen select a DASD device.</dt>
+        <dd>Alternatively zFCP/SCSI disk storage can be selected - if available.</dd>
+        <dd>Overall it's recommended that DASD, as well as zFCP/SCSI disk storage, is tested. Hence if a second z/VM installation is done, it's recommended to use zFCP/SCSI instead of DASD disk storage that time. Usually two zfcp-host devices need to be selected and enabled. Then all available (usually four) paths must be automatically detected (multipath).</dd>
+    <dt>At the network configuration screen, select 'Done' (it should be pre-selected).</dt>
+    <dt>At the filesystem setup screen, select "Use An Entire Disk" (should be pre-selected).</dt>
+    <dt>Choose a disk to install to.</dt>
+    <dt>At the file system summary screen select 'Done' (should be pre-selected).</dt>
+    <dt>At the confirmation dialog, select 'Continue'.</dt>
+    <dt>Fill out the user information dialog, ideally including the import of your SSH keys from launchpad (or github).</dt>
+    <dt>Wait until the installation is complete and select 'Reboot'.</dt>
+    <dt>You may optionally monitor the (re-)boot progress via the console ('Operating System Messages' HMC task).</dt>
+    <dt>Ensure that it's possible to login to the system.</dt>
+    <dt>Ensure that you can run commands with sudo (like for example 'sudo apt update').</dt>
+    <dt>Ensure that the correct s390x devices were configured (like for example with 'lszdev --online').</dt>
+    <dt>Check that the correct SSH keys have been imported by SSHing into the machine or looking at ~/.ssh .</dt>
+</dl>
+<strong>If all actions produce the expected results listed, please <a href="results#add_result">submit</a> a 'passed' result.
+    If an 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>
+