action #104259
Updated by JERiveraMoya about 2 years ago
## Observation openQA test in scenario sle-15-SP4-Online-ppc64le-select_disk@ppc64le-hmc-4disk fails SPORADICALLY in [validate_first_disk_selection](https://openqa.suse.de/tests/7893357/modules/validate_first_disk_selection/steps/5) In qemu the same boot order holds after reboot, using `*-boot order=c*`. For example here: https://openqa.suse.de/tests/8418089#step/validate_first_disk_selection/8 https://openqa.suse.de/tests/7887648#step/select_disks/1 and https://openqa.suse.de/tests/8405891#step/validate_first_disk_selection/8 https://openqa.suse.de/tests/7887648#step/validate_first_disk_selection/8 For ppc64le PowerVM it was working fine but started to fail, https://openqa.suse.de/tests/7887648#step/select_disks/1 https://openqa.suse.de/tests/7893357#step/select_disks/1 now use sdb instead of sda https://openqa.suse.de/tests/7893357#step/validate_first_disk_selection/5. According to YaST teams IFIR, we can only trust on the UUIDs. ### Acceptance criteria **AC1**: Research about boot order kept after reboot in ppc64le (pVM) **AC2**: Relax validation, only one of the 4 disks have the expected partitioning (as we erase in Unschedule this test suite for pVM https://openqa.suse.de/tests/8420923#step/bootloader_start/59 all the disks at the begining and in the rest of archs they are fresh images for qemu). if doesn't make sense or file a ticket proposing solution.