Hi all,

On Sun, 22 Mar 2020 12:17:08 +0100 Paul Gevers <elb...@debian.org> wrote:
> We're seeing this quite a lot currently on our ci.d.n infrastructure,
> and maybe also on Ubuntu's infra, as reported in bug #908193 (I'm not
> sure if that is actually a duplicate or different.)

Another example:

https://ci.debian.net/data/autopkgtest/testing/amd64/o/openjdk-15/7742200/log.gz

jaxp                 SKIP exit status 77 and marked as skippable
autopkgtest [19:39:42]: ERROR: "rm -rf
/tmp/autopkgtest-lxc.9db11r52/downtmp/jaxp-artifacts
/tmp/autopkgtest-lxc.9db11r52/downtmp/autopkgtest_tmp" failed with
stderr "rm: cannot remove
'/tmp/autopkgtest-lxc.9db11r52/downtmp/autopkgtest_tmp/hotspot/JTwork':
Directory not empty
"

I checked the worker, it had a tree in /tmp with (however, this is
probably from another run):
admin@ci-worker05:/tmp/autopkgtest-lxc._w5283nq/downtmp/autopkgtest_tmp/hotspot/JTwork$
ls -al
total 24
drwxr-xr-x  6 admin admin 4096 Oct 25 15:55 .
drwxr-xr-x  3 admin admin 4096 Oct 25 15:55 ..
drwxr-xr-x  3 admin admin 4096 Oct 25 15:55 classes
drwxr-xr-x 11 admin admin 4096 Oct 25 15:55 runtime
drwxr-xr-x  3 admin admin 4096 Oct 25 15:55 scratch
drwxr-xr-x 12 admin admin 4096 Oct 25 15:55 serviceability

There was one lxc present:
admin@ci-worker05:~$ sudo lxc-ls -f
NAME                        STATE   AUTOSTART GROUPS IPV4 IPV6 UNPRIVILEGED
autopkgtest-oldstable-amd64 STOPPED 0         -      -    -    false
autopkgtest-stable-amd64    STOPPED 0         -      -    -    false
autopkgtest-testing-amd64   STOPPED 0         -      -    -    false
autopkgtest-unstable-amd64  STOPPED 0         -      -    -    false
ci-298-ba5278af             STOPPED 0         -      -    -    false

But I could not start it:admin@ci-worker05:~$ sudo lxc-start ci-298-ba5278af
lxc-start: ci-298-ba5278af: lxccontainer.c: wait_on_daemonized_start:
851 Received container state "ABORTING" instead of "RUNNING"
lxc-start: ci-298-ba5278af: tools/lxc_start.c: main: 329 The container
failed to start
lxc-start: ci-298-ba5278af: tools/lxc_start.c: main: 332 To get more
details, run the container in foreground mode
lxc-start: ci-298-ba5278af: tools/lxc_start.c: main: 335 Additional
information can be obtained by setting the --logfile and --logpriority
options
admin@ci-worker05:~$ sudo lxc-start ci-298-ba5278af --foreground
lxc-start: ci-298-ba5278af: start.c: proc_pidfd_open: 1619 Function not
implemented - Failed to send signal through pidfd

                                                 lxc-start:
ci-298-ba5278af: utils.c: safe_mount: 1225 Permission denied - Failed to
mount "proc" onto "/proc"

                          lxc-start: ci-298-ba5278af: conf.c:
lxc_mount_auto_mounts: 728 Permission denied - Failed to mount "proc" on
"/proc" with flags 14

                        lxc-start: ci-298-ba5278af: conf.c: lxc_setup:
3561 Failed to setup first automatic mounts
                                                      lxc-start:
ci-298-ba5278af: start.c: do_start: 1311 Failed to setup container
"ci-298-ba5278af"
                 lxc-start: ci-298-ba5278af: sync.c: __sync_wait: 62 An
error occurred in another process (expected sequence number 5)
  lxc-start: ci-298-ba5278af: start.c: __lxc_start: 2031 Failed to spawn
container "ci-298-ba5278af"

                            lxc-start: ci-298-ba5278af:
tools/lxc_start.c: main: 329 The container failed to start
lxc-start: ci-298-ba5278af: tools/lxc_start.c: main: 335 Additional
information can be obtained by setting the --logfile and --logpriority
options


Paul


Attachment: signature.asc
Description: OpenPGP digital signature

Reply via email to