QA » openQA Project » openQA Tests » qe-yam

I prefer keep test cases which can not handled by PowerVM setup, at least we can use powerkvm do some software level check. such as:
1)Regarding lvm_multipath, lvm_multipath_encrypted and multipath there is not multipath (just check Kernel job group) enabled for virtualization PowerVM, so we can proceed to remove them.
2)We will be removing yast2_nfs_v{3,4}_{client,server} due there there is not MultiMachine with PowerVM.

as requires OFW parameter to work

What is OFW parameter?

coolgw wrote:

I prefer keep test cases which can not handled by PowerVM setup, at least we can use powerkvm do some software level check. such as:
1)Regarding lvm_multipath, lvm_multipath_encrypted and multipath there is not multipath (just check Kernel job group) enabled for virtualization PowerVM, so we can proceed to remove them.
2)We will be removing yast2_nfs_v{3,4}_{client,server} due there there is not MultiMachine with PowerVM.

For me it is no-go to use virtualization that is not supported, recently I got another progress report with some slow registration process and it is a waste of time to go forward with that with bugs or anything, I believe we can drop test coverage there, if you find a multipath bug you will notice that the developers are not going to fix it or at least it is not going to happen anytime soon and will probably ask you to reproduce it in a strange way, not using openQA.
We should spend some time to investigate how those test cases could be done in PowerVM rather than wasting time with unsupported virtualization, wdyt?

rainerkoenig wrote:

as requires OFW parameter to work

What is OFW parameter?

QEMU Open Firmware is in use

Just for clarification, when we say PowerVM we are talking about the pvm-hmc backend in openQA.

geor wrote:

Just for clarification, when we say PowerVM we are talking about the pvm-hmc backend in openQA.

yes, that one.

JERiveraMoya wrote:

coolgw wrote:

I prefer keep test cases which can not handled by PowerVM setup, at least we can use powerkvm do some software level check. such as:
1)Regarding lvm_multipath, lvm_multipath_encrypted and multipath there is not multipath (just check Kernel job group) enabled for virtualization PowerVM, so we can proceed to remove them.
2)We will be removing yast2_nfs_v{3,4}_{client,server} due there there is not MultiMachine with PowerVM.

For me it is no-go to use virtualization that is not supported, recently I got another progress report with some slow registration process and it is a waste of time to go forward with that with bugs or anything, I believe we can drop test coverage there, if you find a multipath bug you will notice that the developers are not going to fix it or at least it is not going to happen anytime soon and will probably ask you to reproduce it in a strange way, not using openQA.
We should spend some time to investigate how those test cases could be done in PowerVM rather than wasting time with unsupported virtualization, wdyt?

If case can pass, i think we can keep it since
1) no any extra effort needed, so no wast any time
2) provide confidence on test coverage
if case start fail, remove it and we can start open new tickets how to check

mediacheck:
https://openqa.nue.suse.com/tests/9806518
https://openqa.nue.suse.com/tests/9806506
Incomplete on Online&Full media.

releasenotes_origin+unregistered:
It seems send_key('ctrl-shift-alt-x'); but no xterm started, I think the key maybe changed to open xterm on power VM.
https://openqa.nue.suse.com/tests/9806519#step/release_notes_from_url/3

textmode_installation_minimal_role:
https://openqa.nue.suse.com/tests/9799977#step/bootloader_start/27
Can't load image.
After reboot, it need a reconnect_mgmt_console to keep VNC connection.
https://openqa.nue.suse.com/tests/9806520#step/grub_test/2
#####################
With my branch, the grub_test pass on power VM:
http://openqa.nue.suse.com/tests/9812368#step/grub_test/1

gpt:
https://openqa.nue.suse.com/tests/9799977#step/bootloader_start/27

yast_hostname:
https://openqa.nue.suse.com/tests/9806221#step/hostname_inst/4
Different hostname

yast_hostname+dhcp_hostname
https://openqa.nue.suse.com/tests/9806219#step/hostname_inst/5
Different hostname

yast_hostname+linuxrc_hostname:
https://openqa.nue.suse.com/tests/9806220
pass

lvm_multipath:
No multipath support
https://openqa.nue.suse.com/tests/9800204#step/multipath/5

• lvm_multipath_encrypted:
  failed to load image
  https://openqa.nue.suse.com/tests/9806914#live

• multipath:
  No multipath support
  https://openqa.nue.suse.com/tests/9800207#step/multipath/7

• yast2_nfs_v{3,4}_{client,server}
  START_AFTER_TEST=create_hdd_textmode, hard to run

releasenotes_origin+unregistered:
It seems send_key('ctrl-shift-alt-x'); but no xterm started, I think the key maybe changed to open xterm on power VM.
https://openqa.nue.suse.com/tests/9806519#step/release_notes_from_url/3

#################################################
I use developer mode to try to reproduce this issue but failed, I can send key 'ctrl-shift-alt-x' and got the xterm dialog, so this should be a test issue, I will try to add some sleep before sending the key to have a look.

Switch to install shell and create new needles then the release_notes_from_url issue gone, but now it failed here:
http://openqa.nue.suse.com/tests/9849587#step/validate_default_target/6
It seems the system target changed on power VM.

leli wrote:

Switch to install shell and create new needles then the release_notes_from_url issue gone, but now it failed here:
http://openqa.nue.suse.com/tests/9849587#step/validate_default_target/6
It seems the system target changed on power VM.

yes, expected, powerVM doesn't have desktop.

JERiveraMoya wrote:

leli wrote:

Switch to install shell and create new needles then the release_notes_from_url issue gone, but now it failed here:
http://openqa.nue.suse.com/tests/9849587#step/validate_default_target/6
It seems the system target changed on power VM.

yes, expected, powerVM doesn't have desktop.

So need create a new yaml file for this test on powerVM? Cause the schedule/yast/releasenotes_origin+unregistered.yaml have desktop selected. Or just remove this case?

leli wrote:

JERiveraMoya wrote:

leli wrote:

Switch to install shell and create new needles then the release_notes_from_url issue gone, but now it failed here:
http://openqa.nue.suse.com/tests/9849587#step/validate_default_target/6
It seems the system target changed on power VM.

yes, expected, powerVM doesn't have desktop.

So need create a new yaml file for this test on powerVM? Cause the schedule/yast/releasenotes_origin+unregistered.yaml have desktop selected. Or just remove this case?

Created a new yaml to skip select module and select textmode role, pass now, http://openqa.nue.suse.com/tests/9869911#

PR: https://github.com/os-autoinst/os-autoinst-distri-opensuse/pull/15843
MR: https://gitlab.suse.de/qsf-y/qa-sle-functional-y/-/merge_requests/434 submitted.