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.
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_77e2ada1e7 a84929a74ba3b87 153c0ac/ 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 lxc-test- attach lxc-test- autostart lxc-test- cgpath lxc-test- concurrent concurrent- 2) failed... concurrent- 4) failed... concurrent- 1) failed... concurrent- 0) failed... lxc-test- console lxc-test- createtest lxc-test- destroytest lxc-test- shutdowntest lxc-test- startone lxc-test- symlink cgfs_init: 2246 - cgroupfs failed to detect cgroup metadata lxc_spawn: 884 - failed initializing cgroup support __lxc_start: 1121 - failed to spawn 'symtest1' c:lxc_cmd_ rsp_recv: 172 - command get_state failed to receive response c:main: 341 - The container failed to start. lxc-test- ubuntu run_template: 1084 container creation template for lxc-test-ubuntu failed
FAIL: lxc-tests: /usr/bin/
FAIL: lxc-tests: /usr/bin/
FAIL
FAIL: lxc-tests: /usr/bin/
FAIL: lxc-tests: /usr/bin/
Starting the container (lxc-test-
Starting the container (lxc-test-
Starting the container (lxc-test-
Starting the container (lxc-test-
FAIL: lxc-tests: /usr/bin/
FAIL: lxc-tests: /usr/bin/
67: failed to start lxctest1
FAIL: lxc-tests: /usr/bin/
FAIL: lxc-tests: /usr/bin/
68: failed to start lxctest1
FAIL: lxc-tests: /usr/bin/
169: lxctest1 failed to start
FAIL: lxc-tests: /usr/bin/
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:
lxc-start 1483662018.638 ERROR lxc_start - start.c:
lxc-start 1483662018.711 ERROR lxc_start - start.c:
lxc-start 1483662018.711 WARN lxc_commands - commands.
lxc-start 1483662018.712 ERROR lxc_start_ui - lxc_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_container: lxccontainer.c: create_
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_77e2ada1e7 a84929a74ba3b87 153c0ac/ 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.