action #173659
opencoordination #169654: [epic] Create test scenarios for Agama
Add unattended multipath scenario
0%
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
Updated by JERiveraMoya about 1 month ago
- File System_seems_to_have_multipath.png System_seems_to_have_multipath.png added
- File agama_multipath_config.json agama_multipath_config.json added
- Description updated (diff)
Updated by hjluo 24 days ago
tried
MULTIPATH=1
to click the multipath page and get the configure file.tried to use the generated configure file to auto install and it failed at
Cannot accommodate the required filesystem for installation
. the job is https://openqa.suse.de/tests/16156378I've cut the screenshot for the error message.
Updated by hjluo 24 days ago
- So @JERiveraMoya is there any setting missing for my configure file. Thanks
Updated by JERiveraMoya 24 days ago
hjluo wrote in #note-8:
- So @JERiveraMoya is there any setting missing for my configure file. Thanks
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.
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.
Updated by hjluo 21 days ago · Edited
- Today tried to run default_sle with
MULTIPATH=1
when activate pages shows clickYes
and wait the installation to finish. then switched to root-console and found thatagama config show
output same storage. - asked the dev and they said can provide a workaroud for answer file.
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).
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.
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.
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.
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 whileagama 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
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
Updated by hjluo 11 days ago · Edited
- File Screenshot from 2024-12-23 15-46-20.png Screenshot from 2024-12-23 15-46-20.png added
- File Screenshot from 2024-12-23 15-37-41.png Screenshot from 2024-12-23 15-37-41.png added
Now it works with
MULTIPATH=1
and thepre script
, andmultipath -ll
shows the correct topology.I'd draft the formal PR for collect
/run/agama/scripts
and pre_script for multipath.
Updated by JERiveraMoya 1 day ago
- Tags changed from qe-yam-dec-sprint-fy25 to qe-yam-jan-sprint-fy25