Skip to content

Tests

Tests #574

Triggered via schedule October 9, 2024 06:47
Status Failure
Total duration 54m 7s
Artifacts

tests.yml

on: schedule
Matrix: system-tests
Fit to window
Zoom out
Zoom in

Annotations

32 errors and 58 warnings
cgroup (4.0/edge - 20.04)
Process completed with exit code 1.
vm (5.0/edge - 22.04)
Process completed with exit code 1.
vm (5.21/edge - 22.04)
Process completed with exit code 1.
cgroup (latest/edge - 24.04)
Process completed with exit code 1.
cluster (latest/edge - 24.04)
Process completed with exit code 1.
container-copy (latest/edge - 24.04)
Process completed with exit code 1.
container (latest/edge - 24.04)
Process completed with exit code 1.
conversion (latest/edge - 24.04)
Process completed with exit code 1.
cpu-vm (latest/edge - 24.04)
Process completed with exit code 1.
devlxd-container (latest/edge - 24.04)
Process completed with exit code 1.
devlxd-vm (latest/edge - 24.04)
Process completed with exit code 1.
efi-vars-editor-vm (latest/edge - 24.04)
Process completed with exit code 1.
docker (latest/edge - 24.04)
Process completed with exit code 1.
interception (latest/edge - 24.04)
Process completed with exit code 1.
network-ovn (latest/edge - 24.04)
Process completed with exit code 1.
network-routed (latest/edge - 24.04)
Process completed with exit code 1.
snapd (latest/edge - 24.04)
Process completed with exit code 1.
network-bridge-firewall (latest/edge - 24.04)
Process completed with exit code 1.
storage-disks-vm (latest/edge - 24.04)
Process completed with exit code 1.
pylxd (latest/edge - 24.04)
Process completed with exit code 1.
storage-vm lvm-thin (latest/edge - 24.04)
Process completed with exit code 1.
storage-vm zfs (latest/edge - 24.04)
Process completed with exit code 1.
storage-vm dir (latest/edge - 24.04)
Process completed with exit code 1.
storage-buckets (latest/edge - 24.04)
Process completed with exit code 1.
storage-vm lvm (latest/edge - 24.04)
Process completed with exit code 1.
storage-vm btrfs (latest/edge - 24.04)
Process completed with exit code 1.
vm (latest/edge - 24.04)
Process completed with exit code 1.
vm-migration (latest/edge - 24.04)
Process completed with exit code 1.
tpm-vm (latest/edge - 24.04)
Process completed with exit code 1.
qemu-external-vm (latest/edge - 24.04)
Process completed with exit code 1.
vm-nesting (latest/edge - 24.04)
Process completed with exit code 1.
storage-volumes-vm (latest/edge - 24.04)
Process completed with exit code 1.
container (4.0/edge - 22.04)
Instance u1 (default) booted but not fully operational: degraded != running
container (4.0/edge - 22.04)
Ignoring known issue with systemd-remount-fs.service
container (4.0/edge - 22.04)
Instance p1 (default) booted but not fully operational: degraded != running
container (4.0/edge - 22.04)
Ignoring known issue with systemd-remount-fs.service
container (4.0/edge - 22.04)
Instance e1 (default) booted but not fully operational: degraded != running
container (4.0/edge - 22.04)
Ignoring known issue with systemd-remount-fs.service
container (4.0/edge - 22.04)
Instance i1 (default) booted but not fully operational: degraded != running
container (4.0/edge - 22.04)
Ignoring known issue with systemd-remount-fs.service
container (4.0/edge - 22.04)
Instance n1 (default) booted but not fully operational: degraded != running
container (4.0/edge - 22.04)
Ignoring known issue with systemd-remount-fs.service
container (4.0/edge - 20.04)
Instance u1 (default) booted but not fully operational: degraded != running
container (4.0/edge - 20.04)
Ignoring known issue with systemd-remount-fs.service
container (4.0/edge - 20.04)
Instance p1 (default) booted but not fully operational: degraded != running
container (4.0/edge - 20.04)
Ignoring known issue with systemd-remount-fs.service
container (4.0/edge - 20.04)
Instance e1 (default) booted but not fully operational: degraded != running
container (4.0/edge - 20.04)
Ignoring known issue with systemd-remount-fs.service
container (4.0/edge - 20.04)
Instance i1 (default) booted but not fully operational: degraded != running
container (4.0/edge - 20.04)
Ignoring known issue with systemd-remount-fs.service
container (4.0/edge - 20.04)
Instance n1 (default) booted but not fully operational: degraded != running
container (4.0/edge - 20.04)
Ignoring known issue with systemd-remount-fs.service
tpm-vm (5.0/edge - 22.04)
5.0/edge detected, using a shorter name
container (5.0/edge - 22.04)
Instance u1 (default) booted but not fully operational: degraded != running
container (5.0/edge - 22.04)
Ignoring known issue with systemd-remount-fs.service
container (5.0/edge - 22.04)
Instance p1 (default) booted but not fully operational: degraded != running
container (5.0/edge - 22.04)
Ignoring known issue with systemd-remount-fs.service
container (5.0/edge - 22.04)
Instance e1 (default) booted but not fully operational: degraded != running
container (5.0/edge - 22.04)
Ignoring known issue with systemd-remount-fs.service
container (5.0/edge - 22.04)
Instance i1 (default) booted but not fully operational: degraded != running
container (5.0/edge - 22.04)
Ignoring known issue with systemd-remount-fs.service
container (5.0/edge - 22.04)
Instance n1 (default) booted but not fully operational: degraded != running
container (5.0/edge - 22.04)
Ignoring known issue with systemd-remount-fs.service
storage-disks-vm (5.0/edge - 22.04)
5.0/edge detected, using a shorter name
container (5.21/edge - 24.04)
Instance u1 (default) booted but not fully operational: degraded != running
container (5.21/edge - 24.04)
Ignoring known issue with systemd-remount-fs.service
container (5.21/edge - 24.04)
Instance p1 (default) booted but not fully operational: degraded != running
container (5.21/edge - 24.04)
Ignoring known issue with systemd-remount-fs.service
container (5.21/edge - 24.04)
Instance e1 (default) booted but not fully operational: degraded != running
container (5.21/edge - 24.04)
Ignoring known issue with systemd-remount-fs.service
container (5.21/edge - 24.04)
Instance i1 (default) booted but not fully operational: degraded != running
container (5.21/edge - 24.04)
Ignoring known issue with systemd-remount-fs.service
container (5.21/edge - 24.04)
Instance n1 (default) booted but not fully operational: degraded != running
container (5.21/edge - 24.04)
Ignoring known issue with systemd-remount-fs.service
container (5.21/edge - 22.04)
Instance u1 (default) booted but not fully operational: degraded != running
container (5.21/edge - 22.04)
Ignoring known issue with systemd-remount-fs.service
container (5.21/edge - 22.04)
Instance p1 (default) booted but not fully operational: degraded != running
container (5.21/edge - 22.04)
Ignoring known issue with systemd-remount-fs.service
container (5.21/edge - 22.04)
Instance e1 (default) booted but not fully operational: degraded != running
container (5.21/edge - 22.04)
Ignoring known issue with systemd-remount-fs.service
container (5.21/edge - 22.04)
Instance i1 (default) booted but not fully operational: degraded != running
container (5.21/edge - 22.04)
Ignoring known issue with systemd-remount-fs.service
container (5.21/edge - 22.04)
Instance n1 (default) booted but not fully operational: degraded != running
container (5.21/edge - 22.04)
Ignoring known issue with systemd-remount-fs.service
storage-buckets (5.21/edge - 22.04)
Skipping test on ceph until we can integrate with microceph
tpm-vm (5.21/edge - 22.04)
5.21/edge detected, using a shorter name
storage-disks-vm (5.21/edge - 22.04)
5.21/edge detected, using a shorter name
storage-disks-vm (5.21/edge - 24.04)
5.21/edge detected, using a shorter name
storage-buckets (5.21/edge - 24.04)
Skipping test on ceph until we can integrate with microceph
tpm-vm (5.21/edge - 24.04)
5.21/edge detected, using a shorter name