action #123427
Updated by JERiveraMoya about 1 year ago
#### Motivation Perhaps this scenario never worked once we moved from Power KVM to PowerVM ## Observation openQA test in scenario sle-15-SP5-Online-ppc64le-modify_existing_partition@ppc64le-hmc-single-disk fails in [modify_existing_partition](https://openqa.suse.de/tests/10352495/modules/modify_existing_partition/steps/4) We need ## Further details #110773 introduced `modify_existing_partition` for PowerVM. This fails now on PowerVM in Build 66.1, from the linked screenshot above we see an empty partition table. The root cause is probably that the test module calls `run_expert_partitioner` [without an option parameter](https://github.com/os-autoinst/os-autoinst-distri-opensuse/blob/c6beaddfd0ce58f188839d6745f8707522444071/tests/installation/partitioning/modify_existing_partition.pm#L19). So this defaults to ensure that there 'existing' partitions. From what we see inn the screenshot, the 'existing' partitioning is some partitioning really empty, so we cannot delete the disk in https://openqa.suse.de/tests/10352495#step/bootloader_start/33 expert_partitioner won't find any sda2 later what leads to the failure. #### Acceptance criteria **AC1**: Avoid wiping up The interesting question is, why this does not happen on the disk in bootloader **AC2**: If more troubles found, consider other machines, [all tests seem to remove this scenario work](https://openqa.suse.de/tests/overview?arch=&flavor=&machine=&test=&modules=modify_existing_partition&module_re=&distri=sle&version=15-SP5&build=66.1&groupid=129#) except for PowerVM #### Additional information Do not work on this after having more stability with #124047 because with pvm_hmc PowerVM. Nevertheless, the recommondation is quite unsuccessful to boot run the system for `run_expert_partitioner` with the second time for these directly chained jobs. option 'current', so that we start with the current proposal.