Skip to content

Tests

Tests #1544

Triggered via schedule October 8, 2024 06:42
Status Failure
Total duration 46m 23s
Artifacts

tests.yml

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

Annotations

16 errors and 69 warnings
vm (5.0/edge - 22.04)
Process completed with exit code 1.
cgroup (4.0/edge - 22.04)
Process completed with exit code 1.
snapd (4.0/edge - 20.04)
Process completed with exit code 1.
cgroup (5.21/edge - 22.04)
Process completed with exit code 1.
network-routed (5.21/edge - 24.04)
Process completed with exit code 1.
storage-vm lvm-thin (5.0/edge - 22.04)
Process completed with exit code 1.
vm-migration (latest/edge - 24.04)
Process completed with exit code 1.
vm (4.0/edge - 20.04)
Process completed with exit code 1.
storage-vm lvm-thin (5.21/edge - 24.04)
Process completed with exit code 1.
container (4.0/edge - 20.04)
Process completed with exit code 1.
efi-vars-editor-vm (5.21/edge - 22.04)
Process completed with exit code 1.
cluster (4.0/edge - 20.04)
Process completed with exit code 1.
devlxd-vm (5.21/edge - 22.04)
Process completed with exit code 1.
vm-nesting (5.21/edge - 24.04)
Process completed with exit code 1.
network-ovn (5.21/edge - 22.04)
Process completed with exit code 1.
vm-nesting (5.0/edge - 22.04)
Process completed with exit code 1.
storage-buckets (latest/edge - 24.04)
Skipping test on ceph until we can integrate with microceph
storage-buckets (5.21/edge - 22.04)
Skipping test on ceph until we can integrate with microceph
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
tpm-vm (5.21/edge - 22.04)
5.21/edge detected, using a shorter name
tpm-vm (5.0/edge - 22.04)
5.0/edge detected, using a shorter name
storage-disks-vm (5.0/edge - 22.04)
5.0/edge detected, using a shorter name
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
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
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 (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 (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
container (latest/edge - 24.04)
Instance u1 (default) booted but not fully operational: degraded != running
container (latest/edge - 24.04)
Ignoring known issue with systemd-remount-fs.service
container (latest/edge - 24.04)
Instance p1 (default) booted but not fully operational: degraded != running
container (latest/edge - 24.04)
Ignoring known issue with systemd-remount-fs.service
container (latest/edge - 24.04)
Instance e1 (default) booted but not fully operational: degraded != running
container (latest/edge - 24.04)
Ignoring known issue with systemd-remount-fs.service
container (latest/edge - 24.04)
Instance i1 (default) booted but not fully operational: degraded != running
container (latest/edge - 24.04)
Ignoring known issue with systemd-remount-fs.service
container (latest/edge - 24.04)
Instance n1 (default) booted but not fully operational: degraded != running
container (latest/edge - 24.04)
Ignoring known issue with systemd-remount-fs.service
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