Project

General

Profile

Actions
Copy link

action #168928

open

coordination #169657: [epic] Handle test fixes and adjustments

Add DASD to encrypted installation and check why the user requirement were not fulfill

Added by JERiveraMoya 27 days ago. Updated 6 days ago.

Status:
New
Priority:
Normal
Assignee:
-
Target version:
-
Start date:
2024-10-25
Due date:
% Done:

0%

Estimated time:

Description

Motivation

openQA test in scenario sle-16.0-agama-installer-s390x-agama_full_disk_encryption@s390x-zVM fails in
agama

Once we add the workaround of the certificate we found a list of errors in the screenshot contained in the logs, most of the are due we didn't take into account DASD for this scenario, that should be added to typescript automation in the same fashion that for the default scenario in interactive way, although it would be even better to try to add it in unatteneded way with the profile we import (is is really ready regarding feature to do that?). Additionally we saw problems with the user creation which should not happen as the imported profile should provide that info.

Acceptance criteria

  • AC1: Solve the DASD issue in unattended way or if not, interactively.
  • AC2: Solve the issue with the user creation which seems not imported.
Suggestions

Clone the profile once the has the correct configuration in interactive mode.

Related issues 1 (1 open — 0 closed)

Related to qe-yam - action #168925: Include agama cloned profile in logsNew2024-10-25

Actions
Actions
Copy link
 #1

Updated by JERiveraMoya 27 days ago

  • Related to action #168925: Include agama cloned profile in logs added
Actions
Copy link
 #2

Updated by openqa_review 13 days ago

This is an autogenerated message for openQA integration by the openqa_review script:

This bug is still referenced in a failing openQA test: agama_full_disk_encryption
https://openqa.suse.de/tests/15894728#step/agama/1

To prevent further reminder comments one of the following options should be followed:

  1. The test scenario is fixed by applying the bug fix to the tested product or the test is adjusted
  2. The openQA job group is moved to "Released" or "EOL" (End-of-Life)
  3. The bugref in the openQA scenario is removed or replaced, e.g. label:wontfix:boo1234

Expect the next reminder at the earliest in 28 days if nothing changes in this ticket.

Actions
Copy link
 #3

Updated by JERiveraMoya 10 days ago

  • Parent task changed from #163919 to #169657
Actions
Copy link
 #4

Updated by JERiveraMoya 6 days ago

  • Priority changed from High to Normal

Let' have priority normal as we have the hackweek, we can increase it later.

Actions
Copy link

Also available in: Atom PDF