action #168928: Add DASD to unattended installation in Agama - qe-yam - openSUSE Project Management Tool

Custom queries

openQA Infrastructure Project
openqa-review - Closed tickets last updated by openqa-review, last 30 days
QA roadmap long-term
QA SLE functional
QA SLE Functional - closed in last 14 days
QA SLE Functional - High, need to be refined
QA SLE Functional - over cycle time median
QA SLE u
QA SLE y
QA tools (tag not necessary in openQA and subprojects)
QA tools tag (tag not necessary in openQA and subprojects; excluding tickets in "Ready" version as they are already on the backlog)
QAC - Backlog
QE tools team - backlog (dev)
QE tools team - backlog (ready issues)
QE tools team - backlog SLA high
QE tools team - backlog SLA immediate
QE tools team - backlog SLA no immediate/urgent in feedback/blocked
QE tools team - backlog SLA normal
QE tools team - backlog SLA urgent
QE tools team - backlog SLO high
QE tools team - backlog SLO normal
QE tools team - backlog SLO urgent
QE tools team - backlog, high-level view (epics and higher)
QE tools team - backlog, non-reactive work, needs parent
QE tools team - backlog, top-level view (all sagas)
QE tools team - closed within last 14 days
QE tools team - closed within last 60 days
QE tools team - closed yesterday
QE Tools Team - Collaborative Session
QE tools team - due date forecast
QE tools team - exceeding due-date
QE tools team - infrastructure backlog
QE tools team - next - sorted by update time
QE tools team - next issues
QE tools team - non-estimated (unblocked) issues (dev)
QE tools team - non-estimated (unblocked) issues (infra)
QE tools team - ready issues - Workable
QE tools team - ready, not assigned/blocked/low
QE tools team - SLO high forecast
QE tools team - update forecast
QE tools team - updated by priority
QE tools team - what members of the team are working on - Feedback (not-low)
QE Tools Team Backlog By Assignee
QE Yam backlog
QE Yam blocked issues
QE Yam closed yesterday
QE Yam issues IN_PROGRESS
QE Yam new action tickets per day
QE Yam new actions
QE Yam prio high, no updates last 4 weeks
QE Yam prio low & normal, no update for 1 year
QE Yam recjected yesterday
QE Yam resolved yesterday
QE Yam workable actions
soft failure tickets in progress
softfailure tickets resolved
softfailure tickets workable
Tools Team Retrospective
Tools Team Retrospective (not estimated or assigned)

Actions

Copy link

action #168928

closed

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

Add DASD to unattended installation in Agama

Added by JERiveraMoya 4 months ago. Updated 17 days ago.

Status:

Resolved

Priority:

High

Assignee:

leli

Target version:

Start date:

2024-10-25

Due date:

% Done:

Estimated time:

Tags:

qe-yam-jan-sprint-fy25

Description

Motivation¶

We probably need further adjusments in the unattended installation profile to add DASD.
https://openqa.suse.de/tests/16239360

Additionally in the encryption scenarios fails because we import that profile:
openQA test in scenario sle-16.0-agama-installer-s390x-agama_full_disk_encryption@s390x-zVM fails in
agama

Acceptance criteria¶

AC1: Add additional configuration to the unattended profile for DASD in s390x zVM.
AC2: Import in the encrypted scenario such a adjusted profile.

Suggestions¶

Clone the profile once the has the correct configuration in interactive mode for a default scenario.

Related issues 1 (0 open — 1 closed)

Related to qe-yam - action #168925: Include agama config attached to the job in openQA

Resolved

leli

2024-10-25

Actions

Issue # Delay: days Cancel

History
Notes
Property changes

Actions

Copy link

Updated by JERiveraMoya 4 months ago

Related to action #168925: Include agama config attached to the job in openQA added

Actions

Copy link

Updated by openqa_review 3 months 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:

The test scenario is fixed by applying the bug fix to the tested product or the test is adjusted
The openQA job group is moved to "Released" or "EOL" (End-of-Life)
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

Updated by JERiveraMoya 3 months ago

Parent task changed from #163919 to #169657

Actions

Copy link

Updated by JERiveraMoya 3 months ago

Priority changed from High to Normal

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

Actions

Copy link

Updated by openqa_review 3 months 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@s390x-zVM
https://openqa.suse.de/tests/16024899#step/agama/1

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

The test scenario is fixed by applying the bug fix to the tested product or the test is adjusted
The openQA job group is moved to "Released" or "EOL" (End-of-Life)
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

Updated by JERiveraMoya 2 months ago

Tags set to qe-yam-jan-sprint-fy25
Subject changed from Add DASD to encrypted installation and check why the user requirement were not fulfill to Add DASD to unattended installation in Agama
Description updated (diff)
Status changed from New to Workable
Priority changed from Normal to High

Actions

Copy link

Updated by JERiveraMoya 2 months ago

Tags changed from qe-yam-jan-sprint-fy25 to qe-yam-dec-sprint-fy25

Actions

Copy link

Updated by leli about 2 months ago

Status changed from Workable to In Progress
Assignee set to leli

Actions

Copy link

Updated by leli about 2 months ago

For this unattended test, https://openqa.suse.de/tests/16239360#step/boot_agama/22 it failed for two agama.auto in parameters which caused agama profile check failed.

Dec 18 14:28:28 osdzvm13.oqa.prg2.suse.org agama-auto[2746]: + '[' -z http://worker33.oqa.prg2.suse.org:20033/jQh2WHWBxJeWN_uf/files/yam/a ']'
Dec 18 14:28:28 osdzvm13.oqa.prg2.suse.org agama-auto[2746]: + echo 'Using the profile at http://worker33.oqa.prg2.suse.org:20033/jQh2WHWBxJeWN_uf/files/yam/a'
Dec 18 14:28:28 osdzvm13.oqa.prg2.suse.org agama-auto[2746]: Using the profile at http://worker33.oqa.prg2.suse.org:20033/jQh2WHWBxJeWN_uf/files/yam/a
Dec 18 14:28:28 osdzvm13.oqa.prg2.suse.org agama-auto[2746]: + case "$url" in
Dec 18 14:28:28 osdzvm13.oqa.prg2.suse.org agama-auto[2746]: + /usr/bin/agama profile import http://worker33.oqa.prg2.suse.org:20033/jQh2WHWBxJeWN_uf/files/yam/a
Dec 18 14:28:29 osdzvm13.oqa.prg2.suse.org agama-auto[2762]: Anyhow([22] HTTP response code said error (The requested URL returned error: 404))

After fix the conflict for dasd format in a branch, https://openqa.suse.de/tests/16261947#step/reconnect_mgmt_console/10 the test now failed for known bug https://bugzilla.suse.com/show_bug.cgi?id=1234264

Actions

Copy link

#10

Updated by leli about 2 months ago · Edited

For the agama_full_disk_encryption, the job link seems removed, anyway I can find it in development group https://openqa.suse.de/tests/16261926#step/agama/5. In puppeteer log it shown 'There is no suitable device for installation', maybe need setup dasd disk for installation, I will try to verify it.

Actions

Copy link

#11

Updated by leli about 2 months ago

Asked this issue in proj_agama, https://suse.slack.com/archives/C02TLF25571/p1734683980138019. it seems a timing issue, I will try to wait 5m after 'import profile' to start installation.

Actions

Copy link

#12

Updated by leli about 2 months ago

Compared the dmesg log for this failed test and a passed unattended test https://openqa.suse.de/tests/16302769#, found something different for dasd: . I'm not very familiar about dasd, not sure whether the meaning for the different output. BTW, wait 5m won't help, same issue https://openqa.suse.de/tests/16303725#step/agama/5.

failed 'import profile':
Dec 20 05:07:52 osdzvm01.oqa.prg2.suse.org kernel: dasd-eckd 0.0.0150: DASD with 4 KB/block, 43273440 KB total size, 48 KB/track, compatible disk layout
Dec 20 05:07:52 osdzvm01.oqa.prg2.suse.org kernel: dasda:
Dec 20 05:07:52 osdzvm01.oqa.prg2.suse.org kernel: dasd-eckd 0.0.0150: A channel path to the device has become operational
Dec 20 05:07:52 osdzvm01.oqa.prg2.suse.org kernel: dasda:VOL1/ 0X0150:
Dec 20 05:07:52 osdzvm01.oqa.prg2.suse.org kernel: dasda:VOL1/ 0X0150:
Dec 20 05:07:52 osdzvm01.oqa.prg2.suse.org kernel: dasda:VOL1/ 0X0150:

passed unattended test:
Dec 26 23:44:42 localhost kernel: dasd-eckd 0.0.0150: A channel path to the device has become operational
Dec 26 23:44:42 localhost kernel: qeth: loading core functions
Dec 26 23:44:42 localhost kernel: dasd-eckd 0.0.0150: A channel path to the device has become operational
Dec 26 23:44:42 localhost kernel: qeth: register layer 3 discipline
Dec 26 23:44:42 localhost kernel: qeth 0.0.0800: CHID: ff00 CHPID: 0
Dec 26 23:44:42 localhost kernel: qeth 0.0.0802: qdio: OSA on SC 2 using AI:1 QEBSM:0 PRI:1 TDD:1 SIGA:RW
Dec 26 23:44:42 localhost kernel: dasd-eckd 0.0.0150: New DASD 3390/0C (CU 3990/01) with 60102 cylinders, 15 heads, 224 sectors
Dec 26 23:44:42 localhost kernel: dasd-eckd 0.0.0150: DASD with 4 KB/block, 43273440 KB total size, 48 KB/track, compatible disk layout
Dec 26 23:44:42 localhost kernel: dasda:VOL1/ 0X0150: dasda1 dasda2 dasda3

Actions

Copy link

#13