Project

General

Profile

Actions

action #173659

open

coordination #169654: [epic] Create test scenarios for Agama

Add unattended multipath scenario

Added by JERiveraMoya about 1 month ago. Updated 1 day ago.

Status:
In Progress
Priority:
High
Assignee:
Target version:
-
Start date:
2024-12-03
Due date:
% Done:

0%

Estimated time:

Description

Motivation

Adding MULTIPATH=1 in an openQA job we can have virtualized multipath out of the box, in OSD just adding that setting, in O3 for example using worker 64bit-multipath.

Acceptance criteria
  • AC1: Unattended multipath scenario is created for openSUSE (tumbleweed, Leap) and SLE 16.
  • AC2: Existing validation for multipath is added.
Additional information

Compare with the scenario for sles 15 in YaST job group.
Attached screenshot of the first screen appearing in the interactive installation and the corresponding collected agama config. It is only and example of how the agama config looks in that moment, it is recommended for each product you create the corresponding agama config in case the syntax is different.


Files

System_seems_to_have_multipath.png (20.8 KB) System_seems_to_have_multipath.png JERiveraMoya, 2024-12-03 11:54
agama_multipath_config.json (1.39 KB) agama_multipath_config.json JERiveraMoya, 2024-12-03 11:54
Screenshot from 2024-12-10 16-57-01.png (80.8 KB) Screenshot from 2024-12-10 16-57-01.png Cannot accommodate the required filesystem for installation hjluo, 2024-12-10 09:16
Screenshot from 2024-12-23 15-46-20.png (15.9 KB) Screenshot from 2024-12-23 15-46-20.png hjluo, 2024-12-23 07:43
Screenshot from 2024-12-23 15-37-41.png (4.37 KB) Screenshot from 2024-12-23 15-37-41.png hjluo, 2024-12-23 07:43
Actions #2

Updated by leli 28 days ago

  • Status changed from Workable to In Progress
  • Assignee set to leli
Actions #3

Updated by JERiveraMoya 28 days ago

  • Status changed from In Progress to Workable
Actions #4

Updated by JERiveraMoya 28 days ago

  • Assignee deleted (leli)
Actions #5

Updated by hjluo 24 days ago

  • Status changed from Workable to In Progress
  • Assignee set to hjluo
Actions #6

Updated by hjluo 24 days ago

Actions #8

Updated by hjluo 24 days ago

Actions #9

Updated by JERiveraMoya 24 days ago

hjluo wrote in #note-8:

Please, use Slack channel for technical doubts and discussion.
(you need to create the profile for latest version as recommended in the ticket description)
For ticket directions or guidance is fine if you use progress.

Actions #10

Updated by hjluo 23 days ago

OK, I'll turn to slack for discussion. and I've generated profile as description in this job. thanks

Actions #11

Updated by hjluo 22 days ago

  • Now try to generate autoyast profile from yast lvm on 15sp7 case and compare it with the json profile from agama manual test.
Actions #12

Updated by hjluo 21 days ago · Edited

  1. Today tried to run default_sle with MULTIPATH=1 when activate pages shows click Yes and wait the installation to finish. then switched to root-console and found that agama config show output same storage.
  2. asked the dev and they said can provide a workaroud for answer file.
Actions #13

Updated by JERiveraMoya 18 days ago

According to developers we should include in logs the content of /run/agama/scripts attached in openQA.
Let's try to include this in this ticket if possible. Take into account that it shouldn't fail if the folder is empty (for other installation is empty).

Actions #14

Updated by hjluo 18 days ago

JERiveraMoya wrote in #note-13:

According to developers we should include in logs the content of /run/agama/scripts attached in openQA.
Let's try to include this in this ticket if possible. Take into account that it shouldn't fail if the folder is empty (for other installation is empty).,

You mean to collect the log from /run/agama/scripts output? I'd try to collect that log.

Actions #15

Updated by JERiveraMoya 18 days ago

hjluo wrote in #note-14:

JERiveraMoya wrote in #note-13:

According to developers we should include in logs the content of /run/agama/scripts attached in openQA.
Let's try to include this in this ticket if possible. Take into account that it shouldn't fail if the folder is empty (for other installation is empty).,

You mean to collect the log from /run/agama/scripts output? I'd try to collect that log.

yes, it is not a log file, they are referring to grab all content of that folder, it should be some example in openQA to borrow.

Actions #16

Updated by hjluo 17 days ago

JERiveraMoya wrote in #note-15:

hjluo wrote in #note-14:

JERiveraMoya wrote in #note-13:

According to developers we should include in logs the content of /run/agama/scripts attached in openQA.
Let's try to include this in this ticket if possible. Take into account that it shouldn't fail if the folder is empty (for other installation is empty).,

You mean to collect the log from /run/agama/scripts output? I'd try to collect that log.

yes, it is not a log file, they are referring to grab all content of that folder, it should be some example in openQA to borrow.
got it, thanks a lot.

Actions #17

Updated by hjluo 16 days ago

  • Asked dev and use the pre script to active mutltipath service as workaround.
  • Now multipathd.socket and multipathd [all activated] before probing. (https://openqa.suse.de/tests/16203240#step/agama_auto/17) at the end of the installation, but multipath -l gave me nothing while agama config show shows /dev/vda was used for disk
  • from Knut Anderssen

so, probably the problem is that the probing is arleady done when multipath is activated.
I should finish current PBI which should solve the issue definitely as well as the profile should support a multipath activation itsef

Actions #18

Updated by hjluo 14 days ago · Edited

  • Knut Anderssen found 1 errro in the configure file and send me a new pre script.
"scripts": {
      "pre": [
         {
            "body": "#!/bin/bash\nif ! systemctl status multipathd ; then\n  echo \"Activating multipath\"\n  systemctl start multipathd.socket\n  systemctl start multipathd\n  sleep 1\nfi\n",
            "name": "activate multipath"
         }
      ]
   },

but after installation it shows multipath not found

Actions #19

Updated by pcervinka 14 days ago

hjluo wrote in #note-18:

but after installation it shows multipath not found

Job is missing MULTIPATH=1.

Actions #20

Updated by hjluo 11 days ago · Edited

pcervinka wrote in #note-19:

hjluo wrote in #note-18:

but after installation it shows multipath not found

Job is missing MULTIPATH=1.

OK, thanks, I'm think of the same idea with compare to the manual test. will try to verify it.

Updated by hjluo 11 days ago · Edited

  • Now it works with MULTIPATH=1 and the pre script, and multipath -ll shows the correct topology.

  • I'd draft the formal PR for collect /run/agama/scripts and pre_script for multipath.

Actions #23

Updated by JERiveraMoya 1 day ago

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

Also available in: Atom PDF