Mailinglist Archive: opensuse-buildservice (81 mails)

< Previous Next >
Worker code does not initialize correctly for older targets, was: Re: [opensuse-buildservice] Packages scheduled
On Fri, 16 Jun 2017 12:30:52 +0200
Mathias Radtke <m.radtke@xxxxxx> wrote:

On 16.06.2017 11:48, Mathias Radtke wrote:

On 16.06.2017 11:37, Stefan Botter wrote:
On Fri, 16 Jun 2017 11:18:08 +0200
Mathias Radtke <m.radtke@xxxxxx> wrote:
My obs server contains my workers.
The only external workers are the ARM ones.

Currently the OBS server hat the following obs packages installed

rpm -qa | grep obs
obs-server-2.8.1-2.1.noarch
:
After the last update it did even build some packages.
As for today it doesn't

Additional Information

The ARM builds on the external worker are running fine.
Only the internal worker are affected

I have an update on my situation:
Builds for Tumbleweed are building fine, whereas builds for - at
least - openSUSE 12.3, openSUSE 13.1, openSUSE 13.2 are not building.

Setup of the kvm machine seems to be not working correctly:

======
Ä 12sÜ ### WATCHDOG MARKER START ###
Ä 12sÜ booting kvm...
Ä 12sÜ linux64 /usr/bin/qemu-kvm -nodefaults -no-reboot -nographic
-vga none -object rng-random,filename=/dev/random,id=rng0 -device
virtio-rng-pci,rng=rng0 -runas qemu -cpu host -mem-prealloc -mem-path
/dev/hugetlbfs -net none -kernel /boot/vmlinuz -initrd /boot/initrd -append
root=/dev/disk/by-id/virtio-0 rootfstype=ext3
rootflags=data=writeback,nobarrier,commit=150,noatime panic=1 quiet no-kvmclock
nmi_watchdog=0 rw rd.driver.pre=binfmt_misc elevator=noop console=ttyS0
init=/.build/build -m 1994 -drive
file=/var/cache/obs/worker/root_2/root,format=raw,if=none,id=disk,serial=0,cache=unsafe
-device virtio-blk-pci,drive=disk -drive
file=/var/cache/obs/worker/root_2/swap,format=raw,if=none,id=swap,serial=1,cache=unsafe
-device virtio-blk-pci,drive=swap -serial stdio -smp 2
Ä 23sÜ ÄFAILEDÜ Failed to start Setup Virtual Console.
Ä 23sÜ See 'systemctl status systemd-vconsole-setup.service' for
details.
Ä 23sÜ Ä OK Ü Started dracut cmdline hook.
Ä 23sÜ Starting dracut pre-udev hook...
Ä 24sÜ Ä OK Ü Started dracut pre-udev hook.
Ä 24sÜ Starting udev Kernel Device Manager...
Ä 24sÜ Ä OK Ü Started udev Kernel Device Manager.
Ä 24sÜ Starting dracut pre-trigger hook...
Ä 24sÜ Ä OK Ü Started dracut pre-trigger hook.
Ä 24sÜ Starting udev Coldplug all Devices...
Ä 24sÜ Ä OK Ü Started udev Coldplug all Devices.
Ä 24sÜ Starting Show Plymouth Boot Screen...
Ä 24sÜ Starting dracut initqueue hook...
Ä 24sÜ Ä OK Ü Reached target System Initialization.
Ä 24sÜ Ä OK Ü Started Show Plymouth Boot Screen.
Ä 24sÜ Ä OK Ü Started Forward Password Requests to Plymouth
Directory Watch.
Ä 24sÜ Ä OK Ü Reached target Paths.
Ä 24sÜ Ä OK Ü Reached target Basic System.
Ä 25sÜ Ä OK Ü Found device /dev/disk/by-id/virtio-0.
======

There it stops, until after approx. 120s
dracut-initqueue timeout - starting timeout scripts
start and the build aborts.


There seems to be an incompatible change in the last published worker
code, which prohibits correct setup of the vm setup in the worker
instance for older build targets.

I do not know where to report this other than here, perhaps in github,
but my track record of reporting things there is rather poor.


Greetings,

Stefan
--
Stefan Botter zu Hause
Bremen
< Previous Next >