Project

General

Custom queries

Profile

Actions

action #173659

open

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

Add unattended multipath scenario

Added by JERiveraMoya 3 months ago. Updated 29 days ago.

Status:
Feedback
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 3 months ago

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

Updated by JERiveraMoya 3 months ago

  • Status changed from In Progress to Workable
Actions #4

Updated by JERiveraMoya 3 months ago

  • Assignee deleted (leli)
Actions #5

Updated by hjluo 3 months ago

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

Updated by hjluo 3 months ago

Actions #8

Updated by hjluo 3 months ago

Actions #9

Updated by JERiveraMoya 3 months 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 3 months 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 3 months 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 2 months 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 2 months 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 2 months 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 2 months 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 2 months 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 2 months 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 2 months 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 2 months ago

hjluo wrote in #note-18:

but after installation it shows multipath not found

Job is missing MULTIPATH=1.

Actions #20

Updated by hjluo 2 months 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 2 months 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 about 2 months ago

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

Updated by hjluo about 2 months ago

Actions #25

Updated by JERiveraMoya about 2 months ago

PR merged, please setup in corresponding job groups (dev and prod).

Actions #26

Updated by hjluo about 2 months ago · Edited

JERiveraMoya wrote in #note-25:

PR merged, please setup in corresponding job groups (dev and prod).

added sles_default_multipath_unattended for group 607 and 612.

Actions #27

Updated by JERiveraMoya about 2 months ago · Edited

hjluo wrote in #note-26:

JERiveraMoya wrote in #note-25:

PR merged, please setup in corresponding job groups (dev and prod).

added sles_default_multipath_unattended for group 607 and 612.

As the build do not trigger much often in prod, when I mean "add" I'm referring to [add + trigger] them in both job groups so we can have a clear view. Thanks.

Actions #28

Updated by JERiveraMoya about 2 months ago

multipath is already specific, doesn't need *_default_* in the test suite name, could you please drop that?

Actions #29

Updated by hjluo about 2 months ago · Edited

JERiveraMoya wrote in #note-28:

multipath is already specific, doesn't need *_default_* in the test suite name, could you please drop that?

Dropped, but I checked out in prod (612) looks like the pre script is not support as we expected.

Actions #30

Updated by JERiveraMoya about 2 months ago

hjluo wrote in #note-29:

JERiveraMoya wrote in #note-28:

multipath is already specific, doesn't need *_default_* in the test suite name, could you please drop that?

Dropped, but I checked out in prod (612) looks like the pre script is not support as we expected.

neither hashed password or scc yet, prod is behind in features than development, could you try without hashed password, I'm wondering if that makes it fails in the first places and does't process the pre script ?

Actions #31

Updated by JERiveraMoya about 2 months ago

could you also rename with quick PR the jsonnet profile? sle_default_multipath.jsonnet
what is missing in development? https://openqa.suse.de/tests/16362774/

Actions #32

Updated by hjluo about 2 months ago · Edited

JERiveraMoya wrote in #note-31:

could you also rename with quick PR the jsonnet profile? sle_default_multipath.jsonnet
OK. https://github.com/os-autoinst/os-autoinst-distri-opensuse/pull/20900

what is missing in development? https://openqa.suse.de/tests/16362774/
This case sometimes will failed at ask for password this morning. but rerun passed.

Actions #33

Updated by hjluo about 2 months ago · Edited

JERiveraMoya wrote in #note-30:

hjluo wrote in #note-29:

JERiveraMoya wrote in #note-28:

multipath is already specific, doesn't need *_default_* in the test suite name, could you please drop that?

Dropped, but I checked out in prod (612) looks like the pre script is not support as we expected.

neither hashed password or scc yet, prod is behind in features than development, could you try without hashed password, I'm wondering if that makes it fails in the first places and does't process the pre script ?

Just tried and it works with plain password. so should we set one profile for prod or all use plan password? thanks

Actions #34

Updated by JERiveraMoya about 2 months ago

Answering your questions:

  • Run x10 for stability and report problems.
  • Duplicate files with using similar file name convention than in existing solution for other test suites.
Actions #35

Updated by hjluo about 2 months ago · Edited

JERiveraMoya wrote in #note-34:

Answering your questions:

  • Run x10 for stability and report problems.
  • Duplicate files with using similar file name convention than in existing solution for other test suites.
Actions #36

Updated by hjluo about 2 months ago

  • the dev said it's a known bug 1235022 with repository timeout.
  • > Hi, it is known issue with repository timeout. We will need better way to handle it in Agama.
Actions #37

Updated by hjluo about 2 months ago · Edited

I move it here to avoid overlap this message:

Actions #38

Updated by hjluo about 2 months ago

  • so for now, how can we handle plain password in prod group? thanks
Actions #39

Updated by JERiveraMoya about 2 months ago

hjluo wrote in #note-38:

  • so for now, how can we handle plain password in prod group? thanks

Please use Slack in general for your questions, I don't know how much info do you need, and having conversations here is quite ineffective, progress can be used for report 'a bit', decision points, blockers, but Slack is much better tool. Also there you can get support from others, in particular your Scrum Master, because I am the one that read the tickets more to answer, so it might also a bit of a bottle neck to ask too many questions here, I hope it makes sense for you. It will help to make things smooth I believe.

You already have an answer for this in https://progress.opensuse.org/issues/173659#note-34 I believe.

Actions #40

Updated by hjluo about 2 months ago · Edited

  • Now marked failed jobs in prod with this poo, cause in prod group, we are not support pre/post script by now.
Actions #41

Updated by hjluo about 2 months ago · Edited

Actions #42

Updated by hjluo about 1 month ago

  • Status changed from In Progress to Resolved
  • Now with PR to add profile to prod group merged, Set this to resolved.
Actions #43

Updated by openqa_review 29 days ago

  • Status changed from Resolved to Feedback

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

This bug is still referenced in a failing openQA test: sles_multipath_unattended
https://openqa.suse.de/tests/16425024#step/agama_auto/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

Also available in: Atom PDF