Please add more testcases to QA/Tracker daily-live image tests for s390x

Bug #1874135 reported by Frank Heimes
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Ubuntu Test Cases
Undecided
Unassigned
Ubuntu on IBM z Systems
Undecided
Ubuntu Test Case Developers

Bug Description

Since the testcases listed at the QA/Tracker for the s390x daily-live images are quite limited (only a KVM test case - aot), I want to request to add the following additional test and very common use cases:

"Install on LPAR using DASD disk storage"

1) Boot up the daily-live image with the help of the HMC (Hardware Management Console) and open the "Integrated ASCII Console" or use a remote ssh installer session (a temporary installer password can be found in boot log at the console):
   |37.487176| cloud-init¬1873|: installer:BpAGSH2HAMY53AC4cbvZ
2) Choose the desired language
3) At the Zdev Setup screen select an available DASD disk
4) On the network configuration screen, just select Done (it should be selected by default)
5) On the filesystem setup screen, select "Use An Entire Disk" (it should be selected by default)
6) Choose a disk to install to
7) On the file system summary screen select Done (it should be selected by default)
8) In the confirmation dialog, select "Continue" (it should not be selected by default)
9) Fill out the user information, making sure to import your SSH keys from somewhere
10) Wait for the install to complete
11) Reboot the system
12) Ensure that you can log into the system with the username and password you provided
13) Ensure that you can run commands with sudo
14) Check that the correct SSH keys have been imported by SSHing into the machine or looking in ~/.ssh./
15) Check with 'lszdev | grep yes' if the correct DASD disk device is in use (also verify with 'lsdasd' and 'mount | grep \/dev')

"Install on z/VM using using DASD disk storage"

1) Boot up the daily-live image in a 3270 terminal emulator connected to a z/VM guest
2) During bootup look for and remember the line about cloud-inits temporary installation password:
   |37.487176| cloud-init¬1873|: installer:BpAGSH2HAMY53AC4cbvZ
3) Connect to the installer using ssh and the password taken from the boot log:
   ssh installer@<zVM guest IP address>
4) Choose the desired language
5) At the Zdev Setup screen select an available DASD disk
6) On the network configuration screen, just select Done (it should be selected by default)
7) On the filesystem setup screen, select "Use An Entire Disk" (it should be selected by default)
8) Choose a disk to install to
9) On the file system summary screen select Done (it should be selected by default)
10) In the confirmation dialog, select "Continue" (it should not be selected by default)
11) Fill out the user information, making sure to import your SSH keys from somewhere
12) Wait for the install to complete
13) Reboot the system
14) Ensure that you can log into the system with the username and password you provided
15) Ensure that you can run commands with sudo
16) Check that the correct SSH keys have been imported by SSHing into the machine or looking in ~/.ssh./
17) Check with 'lszdev | grep yes' if the correct DASD disk device is in use (also verify with 'lsdasd' and 'mount | grep \/dev')

"Install on LPAR using zFCP disk storage"

1) Boot up the daily-live image with the help of the HMC (Hardware Management Console) and open the "Integrated ASCII Console" or use a remote ssh installer session (a temporary installer password can be found in boot log at the console):
   |37.487176| cloud-init¬1873|: installer:BpAGSH2HAMY53AC4cbvZ
2) Choose the desired language
3) At the Zdev Setup screen select available zfcp-host devices and enable them
   They must automatically detect all available paths (multipath)
4) On the network configuration screen, just select Done (it should be selected by default)
5) On the filesystem setup screen, select "Use An Entire Disk" (it should be selected by default)
6) Choose a disk to install to
7) On the file system summary screen select Done (it should be selected by default)
8) In the confirmation dialog, select "Continue" (it should not be selected by default)
9) Fill out the user information, making sure to import your SSH keys from somewhere
10) Wait for the install to complete
11) Reboot the system
12) Ensure that you can log into the system with the username and password you provided
13) Ensure that you can run commands with sudo
14) Check that the correct SSH keys have been imported by SSHing into the machine or looking in ~/.ssh./
15) Check with 'lszdev | grep yes' if the correct zFCP disk devices are in use (also verify with 'sudo dmsetup ls --tree' and 'mount | grep \/dev')

"Install on z/VM using using zFCP disk storage"

1) Boot up the daily-live image in a 3270 terminal emulator connected to a z/VM guest
2) During bootup look for and remember the line about cloud-inits temporary installation password:
   |37.487176| cloud-init¬1873|: installer:BpAGSH2HAMY53AC4cbvZ
3) Connect to the installer using ssh and the password taken from the boot log:
   ssh installer@<zVM guest IP address>
4) Choose the desired language
5) At the Zdev Setup screen select available zfcp-host devices and enable them
   They must automatically detect all available paths (multipath)
6) On the network configuration screen, just select Done (it should be selected by default)
7) On the filesystem setup screen, select "Use An Entire Disk" (it should be selected by default)
8) Choose a disk to install to
9) On the file system summary screen select Done (it should be selected by default)
10) In the confirmation dialog, select "Continue" (it should not be selected by default)
11) Fill out the user information, making sure to import your SSH keys from somewhere
12) Wait for the install to complete
13) Reboot the system
14) Ensure that you can log into the system with the username and password you provided
15) Ensure that you can run commands with sudo
16) Check that the correct SSH keys have been imported by SSHing into the machine or looking in ~/.ssh./
17) Check with 'lszdev | grep yes' if the correct zFCP disk devices are in use (also verify with 'sudo dmsetup ls --tree' and 'mount | grep \/dev')

Frank Heimes (fheimes)
Changed in ubuntu-z-systems:
assignee: nobody → Ubuntu Test Case Developers (ubuntu-test-case-dev)
Revision history for this message
Brian Murray (brian-murray) wrote :
Revision history for this message
Frank Heimes (fheimes) wrote :

No, I didn't knew - and I was told to open such a ticket here.
Anyway, thanks for pointing to LP git/ubuntu-manual-tests - I'll have a look there...

Frank Heimes (fheimes)
Changed in ubuntu-z-systems:
status: New → In Progress
Revision history for this message
Frank Heimes (fheimes) wrote :

The PR is merged now:
https://code.launchpad.net/~fheimes/ubuntu-manual-tests/+git/ubuntu-manual-tests/+merge/390898
updating status to 'Fix Committed'.
(Waiting with the update to 'Fix Released' until the new testcases finally showed up at http://iso.qa.ubuntu.com.)

Changed in ubuntu-test-cases:
status: New → Fix Committed
Changed in ubuntu-z-systems:
status: In Progress → Fix Committed
Revision history for this message
Frank Heimes (fheimes) wrote :

The additional testcases appeared now at the QA tracker pages:
http://iso.qa.ubuntu.com/qatracker/milestones/413/builds/221692/testcases
Closing this ticket as Fix Released.

Changed in ubuntu-z-systems:
status: Fix Committed → Fix Released
Changed in ubuntu-test-cases:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers