pungi.global.log
[IMAGE_BUILD ] [INFO ] [FAIL] Image build (variant CloudImages, arch *, subvariant AtomicHost) failed, but going on anyway. [IMAGE_BUILD ] [INFO ] ImageBuild task failed: 25619354. See /mnt/koji/compose/branched/Fedora-28-20180310.n.0/logs/aarch64-ppc64le-x86_64/imagebuild-CloudImages-AtomicHost-qcow2-raw-xz.aarch64-ppc64le-x86_64.log for more details.
[IMAGE_BUILD ] [INFO ] [FAIL] Image build (variant CloudImages, arch *, subvariant AtomicHost) failed, but going on anyway. [IMAGE_BUILD ] [INFO ] ImageBuild task failed: 25619366. See /mnt/koji/compose/branched/Fedora-28-20180310.n.0/logs/x86_64/imagebuild-CloudImages-AtomicHost-vagrant-libvirt-vagrant-virtualbox.x86_64.log for more details.
[LIVE_IMAGES ] [INFO ] [FAIL] Live (variant Server, arch armhfp, subvariant Server) failed, but going on anyway. [LIVE_IMAGES ] [INFO ] LiveImage task failed: 25619337. See /mnt/koji/compose/branched/Fedora-28-20180310.n.0/logs/armhfp/liveimage-Fedora-Server-armhfp-28-20180310.n.0.armhfp.log for more details.
[IMAGE_BUILD ] [INFO ] [FAIL] Image build (variant CloudImages, arch *, subvariant Cloud_Base) failed, but going on anyway. [IMAGE_BUILD ] [INFO ] ImageBuild task failed: 25619345. See /mnt/koji/compose/branched/Fedora-28-20180310.n.0/logs/x86_64/imagebuild-CloudImages-Cloud_Base-vagrant-libvirt-vagrant-virtualbox.x86_64.log for more details.
[IMAGE_BUILD ] [INFO ] [FAIL] Image build (variant Labs, arch *, subvariant Python_Classroom) failed, but going on anyway. [IMAGE_BUILD ] [INFO ] ImageBuild task failed: 25619398. See /mnt/koji/compose/branched/Fedora-28-20180310.n.0/logs/i386-x86_64/imagebuild-Labs-Python_Classroom-vagrant-libvirt-vagrant-virtualbox.i386-x86_64.log for more details.
BuildError: package (image) Fedora-AtomicHost not in list for tag f28-updates-candidate
and
BuildError: package (image) Fedora-AtomicHost-Vagrant not in list for tag f28-updates-candidate
This is because we renamed the images from Fedora-Atomic to Fedora-AtomicHost in this PR. I think there is some magic that needs to be done in koji to allow for this.
DEBUG util.py:439: Losetup add /dev/loop0 mapping to /var/tmp/imgcreate-Ne3XZl/tmp-dfetwM/Fedora-Server-armhfp-28-20180310.n.0-sda.raw DEBUG util.py:439: losetup: /var/tmp/imgcreate-Ne3XZl/tmp-dfetwM/Fedora-Server-armhfp-28-20180310.n.0-sda.raw: failed to set up loop device: Device or resource busy DEBUG util.py:439: Unable to create appliance : Failed mount disks : Failed to allocate loop device for '/var/tmp/imgcreate-Ne3XZl/tmp-dfetwM/Fedora-Server-armhfp-28-20180310.n.0-sda.raw' DEBUG util.py:577: Child return code was: 1
looks like more losetup issues.. I don't think I've seen this exact one before though.
anaconda bug: 1553488
BuildError: package (image) Fedora-AtomicHost not in list for tag f28-updates-candidate BuildError: package (image) Fedora-AtomicHost-Vagrant not in list for tag f28-updates-candidate
This is fixed by adding the packages Fedora-AtomicHost and Fedora-AtomicHost-Vagrant to koji
$ koji add-pkg f28 Fedora-AtomicHost Fedora-AtomicHost-Vagrant --owner mohanboddu Adding 2 packages to tag f28 $ koji add-pkg f29 Fedora-AtomicHost Fedora-AtomicHost-Vagrant --owner mohanboddu Adding 2 packages to tag f29
25619345 - Vagrant Cloud Base Image 25619398 - Vagrant python classroom
This is fixed by anaconda-29.3-1. If we can get a fc28 build then we can resolve this issue as well.
Login to comment on this ticket.