Skip to content

tests/storage-vm: Add test for live resizing of VM disks with zfs or lvm pool driver #1542

tests/storage-vm: Add test for live resizing of VM disks with zfs or lvm pool driver

tests/storage-vm: Add test for live resizing of VM disks with zfs or lvm pool driver #1542

Triggered via pull request October 8, 2024 02:09
Status Cancelled
Total duration 7m 25s
Artifacts

tests.yml

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

Annotations

90 errors and 69 warnings
cgroup (4.0/edge - 20.04)
Process completed with exit code 1.
network-ovn (5.21/edge - 22.04)
Canceling since a higher priority waiting request for 'Tests-refs/pull/310/merge-pull_request' exists
network-ovn (5.21/edge - 22.04)
The operation was canceled.
container (latest/edge - 24.04)
Canceling since a higher priority waiting request for 'Tests-refs/pull/310/merge-pull_request' exists
container (latest/edge - 24.04)
The operation was canceled.
container (5.0/edge - 22.04)
Canceling since a higher priority waiting request for 'Tests-refs/pull/310/merge-pull_request' exists
container (5.0/edge - 22.04)
The operation was canceled.
storage-vm btrfs (5.21/edge - 22.04)
Canceling since a higher priority waiting request for 'Tests-refs/pull/310/merge-pull_request' exists
storage-vm btrfs (5.21/edge - 22.04)
The operation was canceled.
storage-vm lvm-thin (latest/edge - 24.04)
Canceling since a higher priority waiting request for 'Tests-refs/pull/310/merge-pull_request' exists
storage-vm lvm-thin (latest/edge - 24.04)
The operation was canceled.
storage-vm btrfs (5.21/edge - 24.04)
Canceling since a higher priority waiting request for 'Tests-refs/pull/310/merge-pull_request' exists
storage-vm btrfs (5.21/edge - 24.04)
The operation was canceled.
storage-volumes-vm (5.0/edge - 22.04)
Canceling since a higher priority waiting request for 'Tests-refs/pull/310/merge-pull_request' exists
storage-volumes-vm (5.0/edge - 22.04)
The operation was canceled.
storage-vm lvm (5.0/edge - 22.04)
Canceling since a higher priority waiting request for 'Tests-refs/pull/310/merge-pull_request' exists
storage-vm lvm (5.0/edge - 22.04)
The operation was canceled.
network-ovn (5.21/edge - 24.04)
Canceling since a higher priority waiting request for 'Tests-refs/pull/310/merge-pull_request' exists
network-ovn (5.21/edge - 24.04)
The operation was canceled.
conversion (latest/edge - 24.04)
Canceling since a higher priority waiting request for 'Tests-refs/pull/310/merge-pull_request' exists
conversion (latest/edge - 24.04)
The operation was canceled.
vm-nesting (latest/edge - 24.04)
Canceling since a higher priority waiting request for 'Tests-refs/pull/310/merge-pull_request' exists
vm-nesting (latest/edge - 24.04)
The operation was canceled.
storage-volumes-vm (latest/edge - 24.04)
Canceling since a higher priority waiting request for 'Tests-refs/pull/310/merge-pull_request' exists
storage-volumes-vm (latest/edge - 24.04)
The operation was canceled.
storage-volumes-vm (5.21/edge - 24.04)
Canceling since a higher priority waiting request for 'Tests-refs/pull/310/merge-pull_request' exists
storage-volumes-vm (5.21/edge - 24.04)
The operation was canceled.
storage-vm lvm-thin (5.0/edge - 22.04)
Canceling since a higher priority waiting request for 'Tests-refs/pull/310/merge-pull_request' exists
storage-vm lvm-thin (5.0/edge - 22.04)
The operation was canceled.
storage-volumes-vm (5.21/edge - 22.04)
Canceling since a higher priority waiting request for 'Tests-refs/pull/310/merge-pull_request' exists
storage-volumes-vm (5.21/edge - 22.04)
The operation was canceled.
storage-vm dir (5.21/edge - 24.04)
Canceling since a higher priority waiting request for 'Tests-refs/pull/310/merge-pull_request' exists
storage-vm dir (5.21/edge - 24.04)
The operation was canceled.
storage-vm dir (5.21/edge - 22.04)
Canceling since a higher priority waiting request for 'Tests-refs/pull/310/merge-pull_request' exists
storage-vm dir (5.21/edge - 22.04)
The operation was canceled.
storage-vm lvm (5.21/edge - 24.04)
Canceling since a higher priority waiting request for 'Tests-refs/pull/310/merge-pull_request' exists
storage-vm lvm (5.21/edge - 24.04)
The operation was canceled.
conversion (5.21/edge - 22.04)
Canceling since a higher priority waiting request for 'Tests-refs/pull/310/merge-pull_request' exists
conversion (5.21/edge - 22.04)
The operation was canceled.
storage-vm zfs (latest/edge - 24.04)
Canceling since a higher priority waiting request for 'Tests-refs/pull/310/merge-pull_request' exists
storage-vm zfs (latest/edge - 24.04)
The operation was canceled.
vm-nesting (5.21/edge - 22.04)
Canceling since a higher priority waiting request for 'Tests-refs/pull/310/merge-pull_request' exists
vm-nesting (5.21/edge - 22.04)
The operation was canceled.
storage-vm dir (5.0/edge - 22.04)
Canceling since a higher priority waiting request for 'Tests-refs/pull/310/merge-pull_request' exists
storage-vm dir (5.0/edge - 22.04)
The operation was canceled.
storage-vm lvm-thin (5.21/edge - 24.04)
Canceling since a higher priority waiting request for 'Tests-refs/pull/310/merge-pull_request' exists
storage-vm lvm-thin (5.21/edge - 24.04)
The operation was canceled.
storage-vm btrfs (latest/edge - 24.04)
Canceling since a higher priority waiting request for 'Tests-refs/pull/310/merge-pull_request' exists
storage-vm btrfs (latest/edge - 24.04)
The operation was canceled.
storage-vm lvm-thin (5.21/edge - 22.04)
Canceling since a higher priority waiting request for 'Tests-refs/pull/310/merge-pull_request' exists
storage-vm lvm-thin (5.21/edge - 22.04)
The operation was canceled.
container (5.21/edge - 22.04)
Canceling since a higher priority waiting request for 'Tests-refs/pull/310/merge-pull_request' exists
container (5.21/edge - 22.04)
The operation was canceled.
container (5.21/edge - 24.04)
Canceling since a higher priority waiting request for 'Tests-refs/pull/310/merge-pull_request' exists
container (5.21/edge - 24.04)
The operation was canceled.
qemu-external-vm (latest/edge - 24.04)
Canceling since a higher priority waiting request for 'Tests-refs/pull/310/merge-pull_request' exists
qemu-external-vm (latest/edge - 24.04)
The operation was canceled.
vm-migration (5.21/edge - 24.04)
Canceling since a higher priority waiting request for 'Tests-refs/pull/310/merge-pull_request' exists
vm-migration (5.21/edge - 24.04)
The operation was canceled.
network-ovn (5.0/edge - 22.04)
Canceling since a higher priority waiting request for 'Tests-refs/pull/310/merge-pull_request' exists
network-ovn (5.0/edge - 22.04)
The operation was canceled.
conversion (5.0/edge - 22.04)
Canceling since a higher priority waiting request for 'Tests-refs/pull/310/merge-pull_request' exists
conversion (5.0/edge - 22.04)
The operation was canceled.
storage-vm zfs (5.0/edge - 22.04)
Canceling since a higher priority waiting request for 'Tests-refs/pull/310/merge-pull_request' exists
storage-vm zfs (5.0/edge - 22.04)
The operation was canceled.
storage-vm zfs (5.21/edge - 22.04)
Canceling since a higher priority waiting request for 'Tests-refs/pull/310/merge-pull_request' exists
storage-vm zfs (5.21/edge - 22.04)
The operation was canceled.
storage-vm dir (latest/edge - 24.04)
Canceling since a higher priority waiting request for 'Tests-refs/pull/310/merge-pull_request' exists
storage-vm dir (latest/edge - 24.04)
The operation was canceled.
storage-vm btrfs (5.0/edge - 22.04)
Canceling since a higher priority waiting request for 'Tests-refs/pull/310/merge-pull_request' exists
storage-vm btrfs (5.0/edge - 22.04)
The operation was canceled.
storage-vm lvm (5.21/edge - 22.04)
Canceling since a higher priority waiting request for 'Tests-refs/pull/310/merge-pull_request' exists
storage-vm lvm (5.21/edge - 22.04)
The operation was canceled.
conversion (5.21/edge - 24.04)
Canceling since a higher priority waiting request for 'Tests-refs/pull/310/merge-pull_request' exists
conversion (5.21/edge - 24.04)
The operation was canceled.
storage-vm lvm (latest/edge - 24.04)
Canceling since a higher priority waiting request for 'Tests-refs/pull/310/merge-pull_request' exists
storage-vm lvm (latest/edge - 24.04)
The operation was canceled.
vm-migration (latest/edge - 24.04)
Canceling since a higher priority waiting request for 'Tests-refs/pull/310/merge-pull_request' exists
vm-migration (latest/edge - 24.04)
The operation was canceled.
vm-nesting (5.21/edge - 24.04)
Canceling since a higher priority waiting request for 'Tests-refs/pull/310/merge-pull_request' exists
vm-nesting (5.21/edge - 24.04)
The operation was canceled.
storage-vm zfs (5.21/edge - 24.04)
Canceling since a higher priority waiting request for 'Tests-refs/pull/310/merge-pull_request' exists
storage-vm zfs (5.21/edge - 24.04)
The operation was canceled.
network-ovn (latest/edge - 24.04)
Canceling since a higher priority waiting request for 'Tests-refs/pull/310/merge-pull_request' exists
vm-migration (5.21/edge - 22.04)
Canceling since a higher priority waiting request for 'Tests-refs/pull/310/merge-pull_request' exists
network-ovn (latest/edge - 24.04)
The operation was canceled.
vm-migration (5.21/edge - 22.04)
The operation was canceled.
vm-nesting (5.0/edge - 22.04)
Canceling since a higher priority waiting request for 'Tests-refs/pull/310/merge-pull_request' exists
vm-nesting (5.0/edge - 22.04)
unable to access 'https://github.com/canonical/lxd-ci/': Failed to connect to github.com port 443 after 133324 ms: Connection timed out
vm-nesting (5.0/edge - 22.04)
The operation was canceled.
storage-buckets (latest/edge - 24.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
tpm-vm (5.0/edge - 22.04)
5.0/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
storage-buckets (5.21/edge - 22.04)
Skipping test on ceph until we can integrate with microceph
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
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
storage-disks-vm (5.21/edge - 22.04)
5.21/edge detected, using a shorter name
storage-disks-vm (5.0/edge - 22.04)
5.0/edge detected, using a shorter name
storage-disks-vm (5.21/edge - 24.04)
5.21/edge detected, using a shorter name
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
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 (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