Hi Bjørn,
On 29.09.23 17:23, Bjørn Lie wrote:
Heads-up people - seems the build workers are on strike.
When checking a scheduled build -> the following msg appears:
waiting for 8 compliant workers (1 of them down) (7 of them bad)
And when a package does try to build - this is a snippet from the logs:
[ 0s] booting kvm...
[ 0s] ### VM INTERACTION START ###
[ 0s] Using UART console
[ 0s] /usr/bin/qemu-kvm -nodefaults -no-reboot -nographic -vga none -cpu
host -M pc,accel=kvm,usb=off,dump-guest-core=off,vmport=off -sandbox on
-bios /usr/share/qemu/qboot.rom -object
rng-random,filename=/dev/random,id=rng0 -device virtio-rng-pci,rng=rng0
-runas qemu -mem-prealloc -mem-path /dev/hugetlbfs -net none -kernel
/boot/vmlinuz -initrd /boot/initrd -append root=/dev/sda rootfstype=ext4
[...]
This goes on and on until
[ 193s] Generating "/run/initramfs/rdsosreport.txt"
[ 193s]
[ 193s]
[ 193s] Entering emergency mode. Exit the shell to continue.
[ 193s] Type "journalctl" to view system logs.
[ 193s] You might want to save "/run/initramfs/rdsosreport.txt" to a USB
stick or /boot
[ 193s] after mounting them and attach it to a bug report.
[ 193s]
[ 193s]
[ 193s] Give root password for maintenance
Is this failing for all builds? Or only for certain distributions?
It seems like some "VMinstall: kernel-obs-build" is missing from the
prjconf (or it is trying to build for a distribution that's not
providing a kernel-obs-build), and the host's initrd is not good enough
for an OBS build VM.
-kernel /boot/vmlinuz --initrd /boot/initrd
You have to be lucky if that works nowadays with hostonly initrds.
--
Stefan Seyfried
"For a successful technology, reality must take precedence over
public relations, for nature cannot be fooled." -- Richard Feynman
_______________________________________________
Packman mailing list
[email protected]
https://lists.links2linux.de/cgi-bin/mailman/listinfo/packman
