pungi.global.log
[ERROR ] [FAIL] Image build (variant AtomicHost, arch ppc64le, subvariant AtomicHost) failed, but going on anyway. [IMAGE_BUILD ] [INFO ] Hardlinking /mnt/koji/packages/Fedora-AtomicHost/29_Update/20190315.0/images/Fedora-AtomicHost-29_Update-20190315.0.aarch64.qcow2 to /mnt/koji/compose/updates/Fedora-29-updates-testing-20190315.0/compose/AtomicHost/aarch64/images/Fedora-AtomicHost-29_Update-20190315.0.aarch64.qcow2
I dont know what happened but the tasks seemed to be stuck, nothing fishy is strace. So, I cancelled it to move forward.
https://koji.fedoraproject.org/koji/taskinfo?taskID=33502088
Same with f29-updates - https://koji.fedoraproject.org/koji/taskinfo?taskID=33502084
possibly related to https://lists.fedoraproject.org/archives/list/infrastructure@lists.fedoraproject.org/message/I4FOG2PX6WNUO72TWIZX6GOUBUEF4H3D/ ? That is one notable change from yesterday I think.
There's an error somewhere:
05:52:41,942 INF progress: Running post-installation scripts 05:52:41,946 INF installation: Task started: Run post installation scripts (17/19) 05:52:41,948 INF kickstart.script: Running kickstart %%post script(s) 05:52:42,081 ERR kickstart.script: Error code 1 running the kickstart script at line 27
anaconda dies, but the vm doesn't exit/failure. ;(
26: sed -i '/^#NAutoVTs=.*/ a\ 27: NAutoVTs=0' /etc/systemd/logind.conf
No idea why that would fail, unless it means 27 lines from the top of the ks?
Looking at the %post, it does lock the root account, but then there's a
cp /etc/skel/.bash* /var/roothome
but I don't see a /var/roothome dir in the installroot?
But why is this hitting ppc64le only ?