There are a lot of failures and containers don't seem to be starting for a variety of reasons. lxc 1.0.8 (what this version of libseccomp was tested against) always failed on armhf according to http://autopkgtest.ubuntu.com/packages/l/lxc/trusty/armhf. 1.0.7 also always failed. 1.0.9 started to pass occasionally, but not reliably.
Case in point: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac /autopkgtest-trusty/trusty/armhf/l/lxc/20161205_235522_59b84@/log.gz uses the libseccomp from the release pocket and it has: $ zgrep -i fail ./log.gz FAIL: lxc-tests: /usr/bin/lxc-test-attach FAIL: lxc-tests: /usr/bin/lxc-test-autostart FAIL FAIL: lxc-tests: /usr/bin/lxc-test-cgpath FAIL: lxc-tests: /usr/bin/lxc-test-concurrent Starting the container (lxc-test-concurrent-2) failed... Starting the container (lxc-test-concurrent-4) failed... Starting the container (lxc-test-concurrent-1) failed... Starting the container (lxc-test-concurrent-0) failed... FAIL: lxc-tests: /usr/bin/lxc-test-console FAIL: lxc-tests: /usr/bin/lxc-test-createtest 67: failed to start lxctest1 FAIL: lxc-tests: /usr/bin/lxc-test-destroytest FAIL: lxc-tests: /usr/bin/lxc-test-shutdowntest 68: failed to start lxctest1 FAIL: lxc-tests: /usr/bin/lxc-test-startone 169: lxctest1 failed to start FAIL: lxc-tests: /usr/bin/lxc-test-symlink lxc-start: lxc_start.c: main: 341 The container failed to start. + pass=fail + '[' fail = pass ']' + pass=fail + '[' fail '!=' pass ']' lxc-start 1483662018.638 ERROR lxc_cgfs - cgfs.c:cgfs_init:2246 - cgroupfs failed to detect cgroup metadata lxc-start 1483662018.638 ERROR lxc_start - start.c:lxc_spawn:884 - failed initializing cgroup support lxc-start 1483662018.711 ERROR lxc_start - start.c:__lxc_start:1121 - failed to spawn 'symtest1' lxc-start 1483662018.711 WARN lxc_commands - commands.c:lxc_cmd_rsp_recv:172 - command get_state failed to receive response lxc-start 1483662018.712 ERROR lxc_start_ui - lxc_start.c:main:341 - The container failed to start. + echo 'FAIL: Test 1: expected pass but container did not.' FAIL: Test 1: expected pass but container did not. FAIL: lxc-tests: /usr/bin/lxc-test-ubuntu lxc_container: lxccontainer.c: create_run_template: 1084 container creation template for lxc-test-ubuntu failed Failed creating ubuntu container FAIL: python3: API SUMMARY: pass=9, fail=12, ignored=5 which are all the same failures as in https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac /autopkgtest-trusty/trusty/armhf/l/lxc/20170106_002110_b403a@/log.gz (the one with this SRU's libseccomp). In other words, this SRU introduced no new regressions in the lxc autopkgtest. ** Tags added: verification-done -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1450642 Title: seccomp missing many new syscalls To manage notifications about this bug go to: https://bugs.launchpad.net/snappy/+bug/1450642/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
