from image-root.s390x.log at https://koji.fedoraproject.org/koji/taskinfo?taskID=115226487
... [ INFO ]: 00:49:20 | Creating config.bootoptions [ INFO ]: 00:49:20 | Syncing system to image [ INFO ]: 00:49:20 | --> Syncing boot data at extra partition [ INFO ]: 00:49:20 | --> Syncing root filesystem data [ INFO ]: 00:49:25 | Cleaning up Disk instance [ ERROR ]: 00:49:26 | KiwiCommandError: mount: stderr: mount: /var/tmp/kiwi_mount_manager.b2jelcz5/boot: mount point does not exist. dmesg(1) may have more information after failed mount system call. , stdout: (no output on stdout)
The error seems consistent across the F-40 and Rawhide composes.
I wonder if it needs /mnt/koji like the regular compose builders or something similar ... @ngompa @kevin
/mnt/koji
When do you need this? (YYYY/MM/DD) ASAP
When is this no longer needed or useful? (YYYY/MM/DD) N/A
If we cannot complete your request, what is the impact? missing cloud images for s390x in the F-40 release
Metadata Update from @phsmoura: - Issue tagged with: investigation, medium-gain, medium-trouble, ops
This may be fixed by https://bodhi.fedoraproject.org/updates/FEDORA-2024-fa154b7d3a (which should go stable tomorrow, and be used for the next nightly).
This will be fixed with https://bodhi.fedoraproject.org/updates/FEDORA-2024-861d939ffc
The equivalent in Rawhide/F41 has been able to successfully build s390x images, so we should be good to go once this lands tonight.
This seems fixed to me.
https://koji.fedoraproject.org/koji/taskinfo?taskID=115722659
for example. ;)
Feel free to re-open if you find anything further.
Metadata Update from @kevin: - Issue close_status updated to: Fixed with Explanation - Issue status updated to: Closed (was: Open)
Right, https://github.com/OSInside/kiwi/commit/2e409ec189385a9d60302d64c6a2e6c8bb2f9e57 looks as the fix to me
Log in to comment on this ticket.