Project

General

Profile

Actions

action #151183

closed

coordination #130075: [epic] Milestone testing for SLE 15 SP6

SLE15 SP6 Beta1 manual testing

Added by rainerkoenig 12 months ago. Updated 12 months ago.

Status:
Resolved
Priority:
Urgent
Assignee:
Target version:
Start date:
2023-11-20
Due date:
% Done:

0%

Estimated time:

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.

Actions #1

Updated by rainerkoenig 12 months ago

  • Description updated (diff)
Actions #2

Updated by rfan1 12 months ago

  • Status changed from Workable to In Progress
Actions #3

Updated by rfan1 12 months ago

Will carry out s390x zkvm installation tests with mentioned in Link

Actions #4

Updated by rainerkoenig 12 months ago

  • Assignee set to rfan1
Actions #5

Updated by rfan1 12 months 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
Actions #6

Updated by rfan1 12 months 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/write

Got 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
Actions #7

Updated by rfan1 12 months ago

  • Status changed from Feedback to Resolved
Actions

Also available in: Atom PDF