On Freitag, 22. September 2017, 08:00:38 CEST wrote Hans-Peter Jansen:
Hi,
after a few weeks of proper operation, we experience a strange OBS behaviour now: a kernel-default package stays in scheduled stage since about one day.
A reboot of the OBS host didn't helped. The logs doesn't show something obvious.
It's a single OBS 2.8.3 host with a few workers, plenty of RAM and cores, with uplinks to OBS and PMBS. The base package kernel-source links to openSUSE.org:Kernel:stable, and built correctly as well as the locally linked kernel-syms. Just the also locally linked kernel-default package misbehaves in the described way.
Any ideas for possible reasons of this behaviour and ways to cure them?
most likely some constraint for the worker is not matching your worker: osc cat Kernel:stable kernel-source _constraints "osc r -v" should report if only a few workers are matching. But the build job should actually fail if you never had a worker matching it ... You may also check via osc checkconstraints --help if you have matching workers. In worst case check your dispatcher logs ... -- Adrian Schroeter email: adrian@suse.de SUSE Linux GmbH, GF: Felix Imendörffer, Jane Smithard, Graham Norton, HRB 21284 (AG Nürnberg) Maxfeldstraße 5 90409 Nürnberg Germany -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner@opensuse.org