December 2018 - openSUSE Build Service

[opensuse-buildservice] Phantom binaries in openSUSE:Factory:PowerPC/standard/ppc/_repository
by Andreas Schwab 13 Dec '18

13 Dec '18

The repository in openSUSE:Factory:PowerPC/standard/ppc contains a lot of binaries that are not originating from any package build. Especially the python{2,3}-pluggy.rpm binaries are obnoxious because they are overriding the ones built from the python-pluggy package. $ osc api build/openSUSE:Factory:PowerPC/standard/ppc/_repository | grep python.-pluggy <binary filename="python2-pluggy.rpm" size="31706" mtime="1513504048" /> <binary filename="python3-pluggy.rpm" size="31974" mtime="1513504048" /> $ osc api build/openSUSE:Factory:PowerPC/standard/ppc/python-pluggy | grep python.-pluggy <binary filename="python2-pluggy-0.7.1-1.1.noarch.rpm" size="38904" mtime="1538147591" /> <binary filename="python3-pluggy-0.7.1-1.1.noarch.rpm" size="39604" mtime="1538147591" /> When I disable useforbuild in the python-pluggy package the phantom binaries disapper, and reenabling useforbuild brings the correct binaries into the repository. But after some time the phantom binaries reappear. Other than that there are about 150 phantom binaries in the repository. Andreas. -- Andreas Schwab, SUSE Labs, schwab(a)suse.de GPG Key fingerprint = 0196 BAD8 1CE9 1970 F4BE 1748 E4D4 88E3 0EEA B9D7 "And now for something completely different." -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

1 1

[opensuse-buildservice] News from OBS UI revamp!
by Saray Cabrera Padron 12 Dec '18

12 Dec '18

People of the Builds! We have done some progress in revamping the user interface of OBS. This time we have focused on project, user and group pages. Please try it out and give us feedback! We'dbe happy to read your comments and make it even better! More details in our blog post: https://openbuildservice.org/2018/12/10/revamping-project-ui/ -- Saray A. Cabrera Padrón | scabrerapadron(a)suse.de | scabrerapadron(a)suse.com Full Stack Web Developer - Open Build Service SUSE Linux GmbH, Maxfeldstr. 5, D-90409 Nürnberg Tel: +49-911-74053-0; Fax: +49-911-7417755; https://www.suse.com/ SUSE Linux GmbH, GF: Felix Imendörffer, Jane Smithard, Graham Norton, HRB 21284 (AG Nürnberg)

4 4

[opensuse-buildservice] Random delays during worker start
by Keil, Karsten 11 Dec '18

11 Dec '18

Hello, In our private OBS instance we use KVM workers on SLE12S-SP3. The build servers are HP DL380 Gen9 with 40 cores with 256GB RAM for big workers, 128 GB Ram for smaller ones. On such HW we running for example 10 instances with 3 Jobs. The Problem is that after the initial install stage here are very often (I would say ~ 1/3 of the builds) huge delays in the start of the VM: A good one: .... [ 10s] booting kvm... [ 10s] ### VM INTERACTION START ### [ 11s] /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 -net n [ 11s] [ 1.063999] dracut-pre-udev[161]: modprobe: FATAL: Module kqemu not found. [ 12s] [ 2.047790] dracut-pre-udev[161]: modprobe: FATAL: Module ibmvscsi not found. [ 12s] [ 2.052451] dracut-pre-udev[161]: modprobe: FATAL: Module ibmveth not found. [ 12s] ### VM INTERACTION END ### [ 12s] 2nd stage started in virtual machine [ 12s] machine type: x86_64 ... Bad looks like: ... [ 11s] booting kvm... [ 12s] ### VM INTERACTION START ### [ 12s] /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 -net n [ 12s] [ 1.437692] dracut-pre-udev[161]: modprobe: FATAL: Module kqemu not found. [ 111s] [ 98.122901] dracut-pre-udev[161]: modprobe: FATAL: Module ibmvscsi not found. [ 112s] [ 99.982451] dracut-pre-udev[161]: modprobe: FATAL: Module ibmveth not found. [ 112s] ### VM INTERACTION END ### [ 112s] 2nd stage started in virtual machine [ 112s] machine type: x86_64 ... This could also up to 300 seconds, I do not really found a relationship to the size of the build jobs or amount of packages to install. Also the build itself seems not to be much slower after the delay. The host itself does not have any high load at these moments, most of CPUs is idle. So my questions are: What exact happens in that stage of the VM start, are there copies of the initial packages ongoing ? Does somebody see similar things ? OBS version is 2.92. Thank you Karsten Keil The information in this e-mail is confidential. The contents may not be disclosed or used by anyone other than the addressee. Access to this e-mail by anyone else is unauthorised. If you are not the intended recipient, please notify Airbus immediately and delete this e-mail. Airbus cannot accept any responsibility for the accuracy or completeness of this e-mail as it has been sent over public networks. If you have any concerns over the content of this message or its Accuracy or Integrity, please contact Airbus immediately. All outgoing e-mails from Airbus are checked using regularly updated virus scanning software but you should take whatever measures you deem to be appropriate to ensure that this message and any attachments are virus free. -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

4 4

[opensuse-buildservice] Only root can link in OBS
by Till Dörges 09 Dec '18

09 Dec '18

Hello all, I have a weird problem with a package on a private OBS (x86-64, 2.9.4). It's basically a C program against some external proprietary lib. On any developer's machine it builds just fine with: ./configure make make install for both openSUSE Leap 42.3 (x86-64) and openSUSE Leap 15.0 (x86-64). I put the sources in OBS with the following in my SPEC file --- snip --- [...] %build %{_configure} %{__make} %install # Don't want to register our ext. lib via /etc/ld.so.conf.d/XXX.conf or similar. # Therefore we go with an rpath for the time being. export NO_BRP_CHECK_RPATH=true %{make_install} [...] --- snip --- Compiling works fine. Problem now is, the %{__make} fails when trying to link the final binary with lots of "undefined reference to" symbols from the external proprietary lib. What does work, is to use root4abuild or similar and then adjust the SPEC file like so sudo %{__make} instead of %{__make}. Obviously I don't want to stick with that, but I have no idea on how to debug this any further. Any hints would be greatly appreciated! Thanks and regards -- Till -- Dipl.-Inform. Till Dörges doerges(a)pre-sense.de Tel. +49 - 40 - 244 2407 - 0 Fax +49 - 40 - 244 2407 - 24 PRESENSE Technologies GmbH Sachsenstr. 5, D-20097 HH Geschäftsführer/Managing Directors AG Hamburg, HRB 107844 Till Dörges, Jürgen Sander USt-IdNr.: DE263765024 -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

2 4

[opensuse-buildservice] Are aarch64 workers broken today?
by Julio González Gil 07 Dec '18

07 Dec '18

I see some of my packages failing to build with the following error (or similar, as /var/cache/obs/worker/root_7/ changes for each package): ---------- [ 15s] ### VM INTERACTION START ### [ 15s] /usr/bin/qemu-system-aarch64 -nodefaults -no-reboot -nographic -vga none -enable-kvm -cpu host -M virt,gic-version=host -object rng- random,filename=/dev/hwrng,id=rng0 -device virtio-rng-device,rng=rng0 -runas qemu -net none -kernel /var/cache/obs/worker/root_7/.mount/boot/kernel -initrd /var/cache/obs/worker/root_7/.mount/boot/initrd -append root=/dev/disk/by-id/ virtio-0 rootfstype=ext4 rootflags=noatime ext4.allow_unsupported=1 kpti=off pti=off spectre_v2=off panic=1 quiet no-kvmclock elevator=noop nmi_watchdog=0 rw rd.driver.pre=binfmt_misc console=ttyAMA0 init=/.build/build -m 4096 -drive file=/var/cache/obs/worker/root_7/ root,format=raw,if=none,id=disk,serial=0,cache=unsafe -device virtio-blk- device,drive=disk -drive file=/var/cache/obs/worker/root_7/ swap,format=raw,if=none,id=swap,serial=1,cache=unsafe -device virtio-blk- device,drive=swap -serial stdio -chardev socket,id=monitor,server,nowait,path=/var/cache/obs/worker/root_7/root.qemu/ monitor -mon chardev=monitor,mode=readline -smp 6 [ 15s] qemu-system-aarch64: -drive file=/var/cache/obs/worker/root_7/ root,format=raw,if=none,id=disk,serial=0,cache=unsafe: 'serial' is deprecated, please use the corresponding option of '-device' instead [ 15s] qemu-system-aarch64: -drive file=/var/cache/obs/worker/root_7/ swap,format=raw,if=none,id=swap,serial=1,cache=unsafe: 'serial' is deprecated, please use the corresponding option of '-device' instead [ 321s] ### WATCHDOG TRIGGERED, KILLING VM ### [ 322s] /var/cache/obs/worker/root_7/root: 6794 [ 322s] qemu-system-aarch64: terminating on signal 15 from pid 13040 () [ 322s] ### VM INTERACTION END ### [ 322s] /var/run/obs/worker/7/build/build-vm: line 462: kill: (6787) - No such process [ 322s] No buildstatus set, either the base system is broken (kernel/initrd/ udev/glibc/bash/perl) [ 322s] or the build host has a kernel or hardware problem... gave up after 13 failed build attempts... ---------- As far as I can tell, the following workers are affected: * obs-arm-1: https://build.opensuse.org/build/ systemsmanagement:Uyuni:Master:Temp/SLE_12/aarch64/python-argparse/_log * obs-arm-2: https://build.opensuse.org/build/ systemsmanagement:Uyuni:Master:SLE12-Uyuni-Client-Tools/SLE_12/aarch64/mgr- daemon/_log * obs-arm-7: https://build.opensuse.org/build/ systemsmanagement:Uyuni:Master:SLE12-Uyuni-Client-Tools/SLE_12/aarch64/ spacewalk-koan/_log and https://build.opensuse.org/build/ systemsmanagement:Uyuni:Master:Temp/SLE_12/aarch64/python3-base/_log I can't see anything reported at https://status.opensuse.org/ -- Julio González Gil <jgonzalez(a)suse.com> Release Engineer SUSE Linux GmbH, Maxfeldstr. 5, D-90409 Nürnberg Tel: +49-911-74053-0; Fax: +49-911-7417755; https://www.suse.com/ SUSE Linux GmbH, GF: Felix Imendörffer, Jane Smithard, Graham Norton, HRB 21284 (AG Nürnberg)

1 1

[opensuse-buildservice] build.opensuse.org: command not found
by Nicolas Quiniou-Briand 05 Dec '18

05 Dec '18

Hello, Thanks for this great service/software ! I'm trying to build a test package on build.opensuse.org [0] but I got this error: ``` [ 68s] /usr/bin/asciidoctor \ [ 68s] -n \ [ 68s] README.asciidoc [ 68s] make: /usr/bin/asciidoctor: Command not found [ 68s] make: *** [html] Error 127 [ 68s] error: Bad exit status from /var/tmp/rpm-tmp.3YzfxW (%build) ``` That's strange because rubygem-asciidoctor-1.5.6.1-1.el7 has been installed before by the worker. I added the EPEL repository to my repositories list. On my laptop, I'm able to build this package in a CentOS 7 VM with rubygem-asciidoctor-1.5.6.1-1.el7 package installed. I didn't find any help in documentations regarding this issue. [0] https://build.opensuse.org/package/live_build_log/home:nqb/hello-doc/CentOS… -- Nicolas Quiniou-Briand -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

4 4

[opensuse-buildservice] OBS Administrator ERROR
by Christof Hanke 03 Dec '18

03 Dec '18

Hi, I get from my private OBS instance mails with subject given above and it says : """ Additional projects in api: ["deleted"] Additional projects in backend: ["xxx", "yyy"] """ How can I clean this up safely? Many thanks, Christof -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

2 2