sinnykumari reported a new issue against the project: `releng` that you are following:
By looking into last few nightly composes for container and cloud on s390x, I observed
that we never had all of the artifacts built successfully in a single compose.
* From Fedora-28-20180317.n.0 - cloud-base and container-minimal-base image built
successfully. container-base image failed
* From Fedora-28-20180317.n.0 - cloud-base and container-base image built successfully.
conatiner-minimal-base image failed.
Similar results from rest of the latest compose.
I did some local run of these images using imagefactory and each time following behavior
has been seen:
* kernel.img and initrd files get downloaded, vm gets launched to start install process.
* vm boots and it reaches at
[ OK ] Reached target System Initialization.
[ OK ] Reached target Basic System.
[ 35.891858] dracut-initqueue: RTNETLINK answers: File exists
[ 76.688981] random: crng init done
[ 427.634076] dracut-initqueue: Warning: dracut-initqueue timeout - starting timeout
[ 625.922797] dracut-initqueue: Warning: dracut-initqueue timeout - starting timeout
[ 625.923855] dracut-initqueue: Warning: Could not boot.
Starting Dracut Emergency Shell...
Warning: /dev/root does not exist
and vm install stops here.
Not sure what is the reason of this behavior. Can it be something related to network
between s390x machine and koji ?
To reply, visit the link below or just reply to this email