action #151183
closedcoordination #130075: [epic] Milestone testing for SLE 15 SP6
SLE15 SP6 Beta1 manual testing
Description
Motivation¶
See parent ticket.
Scope¶
Build 39.1 needs to be tested.
Acceptance criteria¶
AC1: Conduct manual exploratory testing of YaST using corresponding build. Scope is Installer and YaST modules on the installed system.
AC2: Report found issues to Bugzilla with the detailed steps to reproduce and reference it here.
AC3: Briefly describe the covered scenarios in this ticket.
Additional information¶
The kind of testing for this task is Exploratory testing but in case you need inspiration, you can take a look to this spreadsheet, but this activity is time-constrained so just take it as a reference, no need for following it strictly.
As an agreement we don't test all the architecture/backend for each milestone, so we will be rotating the architecture/backend for each milestone, please consider to pick one different for each build. The architecture considered and the instructions for having running the vm in each one of them is in our Manual Testing guide.
Updated by rfan1 about 1 year ago
Will carry out s390x zkvm installation tests with mentioned in Link
Updated by rfan1 about 1 year ago
- Status changed from In Progress to Feedback
No issue found so far based on my tests, one thing to mention here is for lukss crypt tests:
With install boot parameter YAST_LUKS2_AVAILABLE=1, We still need to set each partition to LUKS2 [the default crypt type is still LUKS1]
I will double check with developer on this point
/dev/mapper/cr_root is active and is in use.
type: LUKS2
cipher: aes-xts-plain64
keysize: 512 bits
key location: keyring
device: /dev/vda2
sector size: 512
offset: 32768 sectors
size: 51607552 sectors
mode: read/write
Updated by rfan1 about 1 year ago
rfan1 wrote in #note-5:
No issue found so far based on my tests, one thing to mention here is for lukss crypt tests:
With install boot parameter
YAST_LUKS2_AVAILABLE=1, We still need to set each partition to LUKS2 [the default crypt type is still LUKS1]
I will double check with developer on this point/dev/mapper/cr_root is active and is in use. type: LUKS2 cipher: aes-xts-plain64 keysize: 512 bits key location: keyring device: /dev/vda2 sector size: 512 offset: 32768 sectors size: 51607552 sectors mode: read/writeGot confirmation with yast experts, it was by design.
rfan1 wrote in #note-5:
No issue found so far based on my tests, one thing to mention here is for lukss crypt tests:
With install boot parameter
YAST_LUKS2_AVAILABLE=1, We still need to set each partition to LUKS2 [the default crypt type is still LUKS1]
I will double check with developer on this point/dev/mapper/cr_root is active and is in use. type: LUKS2 cipher: aes-xts-plain64 keysize: 512 bits key location: keyring device: /dev/vda2 sector size: 512 offset: 32768 sectors size: 51607552 sectors mode: read/write
Updated by rfan1 about 1 year ago
More detail information about LUKS2 can be found at:
https://github.com/yast/yast-storage-ng/pull/1245
and
https://yast.opensuse.org/blog/2021-11-24/sprints-135-136