Created attachment 1545132 [details] atomichost_cannot_open_root_device.png AtomicHost 20190315 ppc64le install failure: VFS: Cannot open root device "(null)" ... error -6 as per attached image atomichost_cannot_open_root_device.png problem reported by local ppc64le openQA test with compose 20190315 https://kojipkgs.fedoraproject.org/compose/updates/Fedora-29-updates-20190315.0/compose/AtomicHost/ppc64le/iso/Fedora-AtomicHost-ostree-ppc64le-29-20190315.0.iso No such problem with previous compose 20190314 https://kojipkgs.fedoraproject.org/compose/updates/Fedora-29-updates-20190314.0/compose/AtomicHost/ppc64le/iso/Fedora-AtomicHost-ostree-ppc64le-29-20190314.0.iso I assume this is an iso build problem.
I'm not sure what's going on here. f29-branch hasn't changed since 2/28 and the root argument is still set to an empty string (unlike f30 and rawhide). This error usually means the iso label doesn't match the root line, but on ppc64 we don't set it explicitly so grub2 is supposed to figure it out. Both of these builds are using the same lorax version according to pylorax.log: version is 29.26-1 So whatever changed wasn't lorax. Moving it to grub2 since that's the bootloader used on the ppc64le iso.
Can you show us what the kernel command line options were in the bootloader?
I apologize for your investigation time :( As you pointed out the failure was caused by a bad command line option passed to bootloader. This was caused by an openQA script I locally modified that removed the boot option. I am closing this bug as user error (worksforme) Sorry again.