Public bug reported:
Testing failed on:
amd64:
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/amd64/l/lxd/20210331_002001_322ce@/log.gz
arm64:
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/arm64/l/lxd/20210330_023432_11c32@/log.gz
i386:
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/i386/l/lxd/20210331_001905_1aecd@/log.gz
ppc64el:
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/ppc64el/l/lxd/20210331_001557_b82c6@/log.gz
s390x:
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/s390x/l/lxd/20210331_001215_7b9ae@/log.gz
Starting c1
action=start creation date=2021-03-30T02:42:13+0000 ephemeral=false lvl=eror
msg="Failed starting container" name=c1 stateful=false
t=2021-03-30T02:42:14+0000
error: Error calling 'lxd forkstart c1
/tmp/autopkgtest.mceqas/build.1QA/src/test/tmp.MBH/dyt/containers
/tmp/autopkgtest.mceqas/build.1QA/src/test/tmp.MBH/dyt/logs/c1/lxc.conf':
err='Failed to run: /usr/bin/lxd forkstart c1
/tmp/autopkgtest.mceqas/build.1QA/src/test/tmp.MBH/dyt/containers
/tmp/autopkgtest.mceqas/build.1QA/src/test/tmp.MBH/dyt/logs/c1/lxc.conf: '
lxc 20210330024214.649 ERROR lxc_conf - conf.c:run_buffer:286 - Script exited
with status 137.
lxc 20210330024214.649 ERROR lxc_conf - conf.c:lxc_setup:3356 - failed to run
mount hooks for container 'c1'.
lxc 20210330024214.649 ERROR lxc_start - start.c:do_start:1248 - Failed to
setup container "c1".
lxc 20210330024214.649 ERROR lxc_sync - sync.c:__sync_wait:59 - An error
occurred in another process (expected sequence number 5)
lxc 20210330024214.662 ERROR lxc_start - start.c:__lxc_start:1802 - Failed to
spawn container "c1".
lxc 20210330024214.663 ERROR lxc_container -
lxccontainer.c:wait_on_daemonized_start:804 - Received container state
"ABORTING" instead of "RUNNING"
Try `lxc info --show-log lxd2:c1` for more info
==> Cleaning up
==> Killing LXD at /tmp/autopkgtest.mceqas/build.1QA/src/test/tmp.MBH/zOt
==> Deleting all containers
==> Deleting all images
==> Deleting all profiles
Profile default deleted
Profile docker deleted
==> Checking for locked DB tables
==> Checking for leftover files
==> Checking for leftover DB entries
==> Tearing down directory backend in
/tmp/autopkgtest.mceqas/build.1QA/src/test/tmp.MBH/zOt
==> Killing LXD at /tmp/autopkgtest.mceqas/build.1QA/src/test/tmp.MBH/dyt
==> Deleting all containers
==> Deleting all images
==> Deleting all profiles
Profile default deleted
Profile docker deleted
==> Checking for locked DB tables
==> Checking for leftover files
==> Checking for leftover DB entries
==> Tearing down directory backend in
/tmp/autopkgtest.mceqas/build.1QA/src/test/tmp.MBH/dyt
==> TEST DONE: remote usage
==> Test result: failure
** Affects: lxd (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 arm64 i386 kernel-adt-failure kqa-blocker ppc64el s390x
sru-20210315 xenial
** Tags added: kernel-adt-failure
** Tags added: amd64 arm64 i386 kqa-blocker ppc64el s390x sru-20210315
xenial
** Description changed:
Testing failed on:
- amd64:
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/amd64/l/lxd/20210331_002001_322ce@/log.gz
- arm64:
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/arm64/l/lxd/20210330_023432_11c32@/log.gz
- i386:
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/i386/l/lxd/20210331_001905_1aecd@/log.gz
- ppc64el:
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/ppc64el/l/lxd/20210331_001557_b82c6@/log.gz
- s390x:
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/s390x/l/lxd/20210331_001215_7b9ae@/log.gz
+ amd64:
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/amd64/l/lxd/20210331_002001_322ce@/log.gz
+ arm64:
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/arm64/l/lxd/20210330_023432_11c32@/log.gz
+ i386:
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/i386/l/lxd/20210331_001905_1aecd@/log.gz
+ ppc64el:
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/ppc64el/l/lxd/20210331_001557_b82c6@/log.gz
+ s390x:
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/s390x/l/lxd/20210331_001215_7b9ae@/log.gz
+
+
+
+ Starting c1
+ action=start creation date=2021-03-30T02:42:13+0000 ephemeral=false lvl=eror
msg="Failed starting container" name=c1 stateful=false
t=2021-03-30T02:42:14+0000
+ error: Error calling 'lxd forkstart c1
/tmp/autopkgtest.mceqas/build.1QA/src/test/tmp.MBH/dyt/containers
/tmp/autopkgtest.mceqas/build.1QA/src/test/tmp.MBH/dyt/logs/c1/lxc.conf':
err='Failed to run: /usr/bin/lxd forkstart c1
/tmp/autopkgtest.mceqas/build.1QA/src/test/tmp.MBH/dyt/containers
/tmp/autopkgtest.mceqas/build.1QA/src/test/tmp.MBH/dyt/logs/c1/lxc.conf: '
+ lxc 20210330024214.649 ERROR lxc_conf - conf.c:run_buffer:286 - Script
exited with status 137.
+ lxc 20210330024214.649 ERROR lxc_conf - conf.c:lxc_setup:3356 - failed to
run mount hooks for container 'c1'.
+ lxc 20210330024214.649 ERROR lxc_start - start.c:do_start:1248 - Failed to
setup container "c1".
+ lxc 20210330024214.649 ERROR lxc_sync - sync.c:__sync_wait:59 - An error
occurred in another process (expected sequence number 5)
+ lxc 20210330024214.662 ERROR lxc_start - start.c:__lxc_start:1802 - Failed
to spawn container "c1".
+ lxc 20210330024214.663 ERROR lxc_container -
lxccontainer.c:wait_on_daemonized_start:804 - Received container state
"ABORTING" instead of "RUNNING"
+
+ Try `lxc info --show-log lxd2:c1` for more info
+ ==> Cleaning up
+ ==> Killing LXD at /tmp/autopkgtest.mceqas/build.1QA/src/test/tmp.MBH/zOt
+ ==> Deleting all containers
+ ==> Deleting all images
+ ==> Deleting all profiles
+ Profile default deleted
+ Profile docker deleted
+ ==> Checking for locked DB tables
+ ==> Checking for leftover files
+ ==> Checking for leftover DB entries
+ ==> Tearing down directory backend in
/tmp/autopkgtest.mceqas/build.1QA/src/test/tmp.MBH/zOt
+ ==> Killing LXD at /tmp/autopkgtest.mceqas/build.1QA/src/test/tmp.MBH/dyt
+ ==> Deleting all containers
+ ==> Deleting all images
+ ==> Deleting all profiles
+ Profile default deleted
+ Profile docker deleted
+ ==> Checking for locked DB tables
+ ==> Checking for leftover files
+ ==> Checking for leftover DB entries
+ ==> Tearing down directory backend in
/tmp/autopkgtest.mceqas/build.1QA/src/test/tmp.MBH/dyt
+
+
+ ==> TEST DONE: remote usage
+ ==> Test result: failure
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1921969
Title:
lxd 2.0.11-0ubuntu1~16.04.4 ADT test failure with linux 4.4.0-207.239
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lxd/+bug/1921969/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
