9866 2016-07-01 19:22:20 +0000 Sanity tests fail due to permission problem 2016-07-29 14:49:07 +0000 1 1 5 Infrastructure AutoBuilder autobuilder 2.2 x86 Multiple RESOLVED FIXED Medium+ normal 2.2 M3 1 bill.randle bill.randle infras.ab.watcher Infras.watcher jose.perez.carranza pidge sgw libertad.gonzalez.de.la.cruz --- --- No (bug/feature does not impact docs) oldest_to_newest 63593 0 bill.randle 2016-07-01 19:22:20 +0000 On the new yocto.io AB cluster, the sanity tests are failing, presumably because of a permissions problem (though it could be something else). NOTE: recipe core-image-sato-sdk-1.0-r0: task do_testimage: Started WARNING: core-image-minimal-1.0-r0 do_testimage: Qemu ended unexpectedly, dump data from host is in /tmp/oe-saved-tests/201607011710_qemu ERROR: core-image-minimal-1.0-r0 do_testimage: Function failed: do_testimage ERROR: Logfile of failure stored in: /home/pokybuild/yocto-autobuilder/yocto-worker/nightly-arm/build/build/tmp/work/qemuarm-poky-linux-gnueabi/core-image-minimal/1.0-r0/temp/log.do_testimage.2944 Log data follows: | DEBUG: Executing python function do_testimage | NOTE: rootfs file: /home/pokybuild/yocto-autobuilder/yocto-worker/nightly-arm/build/build/tmp/work/qemuarm-poky-linux-gnueabi/core-image-minimal/1.0-r0/testimage/core-image-minimal-qemuarm-testimage.ext4 | NOTE: Qemu log file: /home/pokybuild/yocto-autobuilder/yocto-worker/nightly-arm/build/build/tmp/work/qemuarm-poky-linux-gnueabi/core-image-minimal/1.0-r0/testimage/qemu_boot_log.20160701171015 | NOTE: SSH log file: /home/pokybuild/yocto-autobuilder/yocto-worker/nightly-arm/build/build/tmp/work/qemuarm-poky-linux-gnueabi/core-image-minimal/1.0-r0/testimage/ssh_target_log.20160701171015 | NOTE: Created listening socket for qemu serial console on: 127.0.0.1:52417 | NOTE: Created listening socket for qemu serial console on: 127.0.0.1:34754 | NOTE: runqemu started, pid is 2950 | NOTE: waiting at most 60 seconds for qemu pid | NOTE: runqemu exited with code 1 | NOTE: Output from runqemu: | Please use simplified serial or kvm options instead | | Continuing with the following parameters: | KERNEL: [/home/pokybuild/yocto-autobuilder/yocto-worker/nightly-arm/build/build/tmp/deploy/images/qemuarm/zImage-qemuarm.bin] | ROOTFS: [/home/pokybuild/yocto-autobuilder/yocto-worker/nightly-arm/build/build/tmp/work/qemuarm-poky-linux-gnueabi/core-image-minimal/1.0-r0/testimage/core-image-minimal-qemuarm-testimage.ext4] | FSTYPE: [ext4] | stty: standard input: Inappropriate ioctl for device | Acquiring lockfile for tap0... | Using preconfigured tap device 'tap0' | If this is not intended, touch /tmp/qemu-tap-locks/tap0.skip to make runqemu skip tap0. | Running qemu-system-arm... | /home/pokybuild/yocto-autobuilder/yocto-worker/nightly-arm/build/build/tmp/sysroots/x86_64-linux/usr/bin/qemu-system-arm -kernel /home/pokybuild/yocto-autobuilder/yocto-worker/nightly-arm/build/build/tmp/deploy/images/qemuarm/zImage-qemuarm.bin -net nic,model=virtio -net tap,vlan=0,ifname=tap0,script=no,downscript=no -M versatilepb -drive file=/home/pokybuild/yocto-autobuilder/yocto-worker/nightly-arm/build/build/tmp/work/qemuarm-poky-linux-gnueabi/core-image-minimal/1.0-r0/testimage/core-image-minimal-qemuarm-testimage.ext4,if=virtio,format=raw -no-reboot -show-cursor -usb -usbdevice tablet -no-reboot -serial tcp:127.0.0.1:52417 -m 128 -serial tcp:127.0.0.1:34754 -append "root=/dev/vda rw console=ttyAMA0,115200 console=tty ip=192.168.7.2::192.168.7.1:255.255.255.0 mem=128M highres=off rootfstype=ext4 console=tty1 console=ttyS0,115200n8 printk.time=1" | qemu-system-arm: -net tap,vlan=0,ifname=tap0,script=no,downscript=no: could not configure /dev/net/tun (tap0): Operation not permitted | Releasing lockfile of preconfigured tap device 'tap0' | stty: standard input: Inappropriate ioctl for device | stty: standard input: Inappropriate ioctl for device | | NOTE: Sending SIGTERM to runqemu | WARNING: Qemu ended unexpectedly, dump data from host is in /tmp/oe-saved-tests/201607011710_qemu | DEBUG: Python function do_testimage finished | ERROR: Function failed: do_testimage 64303 1 bill.randle 2016-07-21 19:34:04 +0000 This is a portion of the strace log for the qemu-arm startup: open("/dev/net/tun", O_RDWR) = 9 ioctl(9, TUNGETFEATURES, 0x7ffcee89ea6c) = 0 ioctl(9, TUNSETVNETHDRSZ, 0x7ffcee89ea68) = -1 EBADFD (File descriptor in bad state) ioctl(9, TUNSETIFF, 0x7ffcee89ea70) = -1 EPERM (Operation not permitted) close(9) = 0 fstat(2, {st_mode=S_IFCHR|0620, st_rdev=makedev(136, 2), ...}) = 0 write(2, "qemu-system-i386: -net tap,vlan="..., 136qemu-system-i386: -net tap,vlan=0,ifname=tap0,script=no,downscript=no: could not configure /dev/net/tun (tap0): Operation not permitted ) = 136 It is the TUNSETIFF ioctl that is causing the problem. It turns out the kernel tun driver looks for the user id AND group id of the process calling that ioctl to match. In our setup, the tap devices are owned by uid 6000 (pokybuild) and group 100 (users). The pokybuild user was not part of the users group. Added pokybuild to the users group and restarted the workers and now the sajnity test is working.