[opensuse-buildservice] python3 setup.py fails
What has changed in the last days in the build VMs that triggers this python3 error? [ 53s] + cd Photini-2016.12.0 [ 53s] + python3 setup.py build [ 53s] Fatal Python error: failed to get random numbers to initialize Python It happens to work in 'graphics', but not in Packman. Olaf
On Mär 16 2017, Olaf Hering <olaf@aepfle.de> wrote:
It happens to work in 'graphics', but not in Packman.
Do your workers have a hw_random device? -object rng-random,filename=/dev/random,id=rng0 -device virtio-rng-pci,rng=rng0 Andreas. -- Andreas Schwab, SUSE Labs, schwab@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@opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner@opensuse.org
On Thu, Mar 16, Andreas Schwab wrote:
On Mär 16 2017, Olaf Hering <olaf@aepfle.de> wrote:
It happens to work in 'graphics', but not in Packman.
Do your workers have a hw_random device?
-object rng-random,filename=/dev/random,id=rng0 -device virtio-rng-pci,rng=rng0
I have no access to the workers. Why would they suddenly need one? Looks like python3 is not fully baked yet. Olaf
On Mär 16 2017, Olaf Hering <olaf@aepfle.de> wrote:
I have no access to the workers.
Read the logfile. Andreas. -- Andreas Schwab, SUSE Labs, schwab@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@opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner@opensuse.org
On Thu, Mar 16, Andreas Schwab wrote:
On Mär 16 2017, Olaf Hering <olaf@aepfle.de> wrote:
I have no access to the workers. Read the logfile.
... [ 5s] BFD: /boot/vmlinuz: Warning: Ignoring section flag IMAGE_SCN_MEM_NOT_PAGED in section .bss [ 9s] ### WATCHDOG MARKER START ### [ 9s] booting kvm... [ 9s] /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=ext4 rootflags=noatime panic=1 quiet no-kvmclock nmi_watchdog=0 rw rd.driver.pre=binfmt_misc elevator=noop console=ttyS0 init=/.build/build -m 1950 -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 [ 16s] FATAL: Module kqemu not found. [ 16s] FATAL: Module ext2 not found. [ 16s] FATAL: Module ext3 not found. [ 16s] WARNING: Failed to connect to lvmetad: No such file or directory. Falling back to internal scanning. [ 16s] Volume group "system" not found [ 16s] WARNING: Failed to connect to lvmetad: No such file or directory. Falling back to internal scanning. [ 16s] Volume group "system" not found [ 16s] Trying manual resume from /dev/system/swap [ 16s] resume device /dev/system/swap not found (ignoring) [ 16s] Trying manual resume from /dev/system/swap [ 16s] resume device /dev/system/swap not found (ignoring) [ 16s] Waiting for device /dev/disk/by-id/virtio-0 to appear: ok [ 16s] fsck from util-linux 2.23.2 [ 16s] [/sbin/fsck.ext4 (1) -- /] fsck.ext4 -a /dev/vda [ 16s] /dev/vda: clean, 3193/1024000 files, 107137/4096000 blocks [ 16s] fsck succeeded. Mounting root device read-write. [ 16s] Mounting root /dev/disk/by-id/virtio-0 [ 16s] mount -o rw,noatime,acl,user_xattr -t ext4 /dev/disk/by-id/virtio-0 /root [ 16s] replacing /etc/mtab with symlink to /proc/self/mounts [ 17s] init /.build/build is not systemd, terminate plymouth [ 17s] ### WATCHDOG MARKER END ### [ 17s] 2nd stage started in virtual machine [ 17s] machine type: x86_64 [ 17s] Setting up swapspace version 1, size = 1024 MiB (1073737728 bytes) [ 17s] no label, UUID=0c681d57-47c0-4ab8-ba68-b8df6e7c0507 [ 17s] swapon: /dev/vdb: found signature [pagesize=4096, signature=swap] [ 17s] swapon: /dev/vdb: pagesize=4096, swapsize=1073741824, devsize=1073741824 [ 17s] swapon /dev/vdb [ 17s] WARNING: udev not running, creating extra device nodes [ 18s] mount: none is already mounted or /proc busy [ 18s] mount: none is already mounted or /dev/pts busy [ 18s] logging output to //.build.log... [ 18s] processing recipe /.build-srcdir/Photini.spec ... [ 18s] init_buildsystem --configdir /.build/configs --cachedir /var/cache/build /.build-srcdir/Photini.spec build rpmlint-Factory ... .... Olaf
On Thu, 16 Mar 2017 09:41:08 +0100 Olaf Hering <olaf@aepfle.de> wrote:
What has changed in the last days in the build VMs that triggers this python3 error?
[ 53s] + cd Photini-2016.12.0 [ 53s] + python3 setup.py build [ 53s] Fatal Python error: failed to get random numbers to initialize Python
It happens to work in 'graphics', but not in Packman.
1337 13:17:06.361953 getrandom(0x7f9d23bbd770, 24, 0) = -1 ENOSYS (Function not implemented) 1337 13:17:06.362176 write(2, "Fatal Python error: failed to get random numbers to initialize Python\n", 70) = 70 Leap does this, and succeeds: 1283 13:17:05.902494 open("/dev/urandom", O_RDONLY|O_CLOEXEC) = 3 Olaf
hello, On 17.3.2017 14:20, Olaf Hering wrote:
On Thu, 16 Mar 2017 09:41:08 +0100 Olaf Hering <olaf@aepfle.de> wrote:
What has changed in the last days in the build VMs that triggers this python3 error?
(...)
1337 13:17:06.361953 getrandom(0x7f9d23bbd770, 24, 0) = -1 ENOSYS (Function not implemented) 1337 13:17:06.362176 write(2, "Fatal Python error: failed to get random numbers to initialize Python\n", 70) = 70
Thanks for the pointers, you're apparently the first person who tried to run our new python on an old kernel. Upstream is aware of the problem and it is going to be fixed in 3.6.1 scheduled for Monday, so i'll prepare an update... note that the same problem most likely exists in python 2 regards m.
Leap does this, and succeeds: 1283 13:17:05.902494 open("/dev/urandom", O_RDONLY|O_CLOEXEC) = 3
Olaf
Am 17. März 2017 19:38:44 MEZ schrieb jan matejek <jmatejek@suse.com>:
old kernel.
How old is "old"? It is 4.10.x. OpenQA is not complaining because there are snapshots every other day. Olaf -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner@opensuse.org
On 17.3.2017 19:48, Olaf Hering wrote:
Am 17. März 2017 19:38:44 MEZ schrieb jan matejek <jmatejek@suse.com>:
old kernel.
How old is "old"? It is 4.10.x. OpenQA is not complaining because there are snapshots every other day.
On 17.3.2017 14:20, Olaf Hering wrote: (...) 1337 13:17:06.361953 getrandom(0x7f9d23bbd770, 24, 0) = -1 ENOSYS (Function not implemented)
old enough that it doesn't implement the getrandom() syscall, apparently? (should have existed since 3.17) or maybe something different is going on in your testing and on the actual failing machine m.
Olaf
On 17.3.2017 19:53, jan matejek wrote:
On 17.3.2017 19:48, Olaf Hering wrote:
Am 17. März 2017 19:38:44 MEZ schrieb jan matejek <jmatejek@suse.com>:
old kernel.
How old is "old"? It is 4.10.x. OpenQA is not complaining because there are snapshots every other day.
On 17.3.2017 14:20, Olaf Hering wrote: (...) 1337 13:17:06.361953 getrandom(0x7f9d23bbd770, 24, 0) = -1 ENOSYS (Function not implemented)
old enough that it doesn't implement the getrandom() syscall, apparently? (should have existed since 3.17)
or maybe something different is going on in your testing and on the actual failing machine
Whatever the reason, though, I suspect the underlying cause to be the same upstream bug (http://bugs.python.org/issue29157): since glibc introduced a "getentropy()" call, Python has been silently using a codepath on Linux that was written for BSD. In the Linux version a fallback to /dev/urandom is present, not so on BSD... we'll see on monday :) m.
Am 17. März 2017 19:53:42 MEZ schrieb jan matejek <jmatejek@suse.com>:
or maybe something different is going on in your testing and on the actual failing machine
It is from the build vm. I added strace python3 and packaged the result. -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner@opensuse.org
On 17 March 2017 at 19:53, jan matejek <jmatejek@suse.com> wrote:
On 17.3.2017 19:48, Olaf Hering wrote:
Am 17. März 2017 19:38:44 MEZ schrieb jan matejek <jmatejek@suse.com>:
old kernel.
How old is "old"? It is 4.10.x. OpenQA is not complaining because there are snapshots every other day. openQA for build problem in OBS ?
On 17.3.2017 14:20, Olaf Hering wrote: (...) 1337 13:17:06.361953 getrandom(0x7f9d23bbd770, 24, 0) = -1 ENOSYS (Function not implemented)
old enough that it doesn't implement the getrandom() syscall, apparently? (should have existed since 3.17)
or maybe something different is going on in your testing and on the actual failing machine
m.
Olaf
-- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner@opensuse.org
On Mär 17 2017, Olaf Hering <olaf@aepfle.de> wrote:
Am 17. März 2017 19:38:44 MEZ schrieb jan matejek <jmatejek@suse.com>:
old kernel.
How old is "old"? It is 4.10.x.
Are you sure the worker is using the kernel in kernel-obs-build? Andreas. -- Andreas Schwab, schwab@linux-m68k.org GPG Key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5 "And now for something completely different." -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner@opensuse.org
Am Fri, 17 Mar 2017 21:31:07 +0100 schrieb Andreas Schwab <schwab@linux-m68k.org>:
Are you sure the worker is using the kernel in kernel-obs-build?
It is using the host kernel. ... [ 54s] ==> /proc/version <== [ 54s] Linux version 3.12.67-58-desktop (geeko@buildhost) (gcc version 4.8.1 20130909 [gcc-4_8-branch revision 202388] (SUSE Linux) ) #1 SMP PREEMPT Thu Nov 10 00:01:20 UTC 2016 (d8de7ec) [ 54s] [ 54s] ==> /proc/cpuinfo <== [ 54s] processor : 0 [ 54s] vendor_id : GenuineIntel [ 54s] cpu family : 6 [ 54s] model : 23 [ 54s] model name : Intel(R) Core(TM)2 Quad CPU Q9300 @ 2.50GHz ... Olaf
On Mär 17 2017, Olaf Hering <olaf@aepfle.de> wrote:
Am Fri, 17 Mar 2017 21:31:07 +0100 schrieb Andreas Schwab <schwab@linux-m68k.org>:
Are you sure the worker is using the kernel in kernel-obs-build?
It is using the host kernel.
That needs to be fixed. Andreas. -- Andreas Schwab, schwab@linux-m68k.org GPG Key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5 "And now for something completely different." -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner@opensuse.org
participants (5)
-
Andreas Schwab -
Andreas Schwab -
jan matejek -
Olaf Hering -
Ondřej Súkup