Please, describe the problem here and provide additional information below (if applicable) …
We have added lxc node and while creating lxc container using market places images its giving below error related to block devices not on such as below.
Thu Feb 13 13:49:48 2025 [Z0][VM][I]: New state is ACTIVE
Thu Feb 13 13:49:48 2025 [Z0][VM][I]: New LCM state is PROLOG
Thu Feb 13 13:51:12 2025 [Z0][VM][I]: New LCM state is BOOT
Thu Feb 13 13:51:12 2025 [Z0][VMM][I]: Generating deployment file: /var/lib/one/vms/119/deployment.0
Thu Feb 13 13:51:14 2025 [Z0][VMM][I]: Successfully execute transfer manager driver operation: tm_context.
Thu Feb 13 13:51:15 2025 [Z0][VMM][I]: ExitCode: 0
Thu Feb 13 13:51:15 2025 [Z0][VMM][I]: Successfully execute network driver operation: pre.
Thu Feb 13 13:51:15 2025 [Z0][VMM][I]: ExitCode: 0
Thu Feb 13 13:51:15 2025 [Z0][VMM][I]: Successfully execute virtualization driver operation: /bin/mkdir -p.
Thu Feb 13 13:51:15 2025 [Z0][VMM][I]: ExitCode: 0
Thu Feb 13 13:51:15 2025 [Z0][VMM][I]: Successfully execute virtualization driver operation: /bin/cat - >/var/lib/one//datastores/118/119/vm.xml.
Thu Feb 13 13:51:16 2025 [Z0][VMM][I]: ExitCode: 0
Thu Feb 13 13:51:16 2025 [Z0][VMM][I]: Successfully execute virtualization driver operation: /bin/cat - >/var/lib/one//datastores/118/119/ds.xml.
Thu Feb 13 13:51:17 2025 [Z0][VMM][I]: Command execution fail (exit code: 255): cat << ‘EOT’ | /var/tmp/one/vmm/lxc/deploy ‘/var/lib/one//datastores/118/119/deployment.0’ ‘blrnode1’ 119 blrnode1
Thu Feb 13 13:51:17 2025 [Z0][VMM][I]: deploy: No block device on /var/lib/one/datastores/118/119/mapper/disk.0
Thu Feb 13 13:51:17 2025 [Z0][VMM][I]: deploy: No block device on /var/lib/one/datastores/118/119/mapper/disk.1
Thu Feb 13 13:51:17 2025 [Z0][VMM][I]: sudo lxc-ls
Thu Feb 13 13:51:17 2025 [Z0][VMM][I]: lsblk -o NAME,FSTYPE
Thu Feb 13 13:51:17 2025 [Z0][VMM][I]: lsblk -o NAME,FSTYPE
Thu Feb 13 13:51:17 2025 [Z0][VMM][I]: lsblk -o NAME,FSTYPE
Thu Feb 13 13:51:17 2025 [Z0][VMM][I]: lsblk -o NAME,FSTYPE
Thu Feb 13 13:51:17 2025 [Z0][VMM][I]: sudo -n mount /dev/vg-one-118/lv-one-119-0 /var/lib/one/datastores/118/119/mapper/disk.0
Thu Feb 13 13:51:17 2025 [Z0][VMM][I]: sudo -n bindfs --uid-offset=-9869 --gid-offset=-9869 -o suid /var/lib/one/datastores/118/119/mapper/disk.0 /var/lib/lxc-one/119/disk.0
Thu Feb 13 13:51:17 2025 [Z0][VMM][I]: sudo -n losetup --find --show /var/lib/one/datastores/118/119/disk.1
Thu Feb 13 13:51:17 2025 [Z0][VMM][I]: lsblk -o NAME,FSTYPE
Thu Feb 13 13:51:17 2025 [Z0][VMM][I]: sudo -n mount /dev/loop0 /var/lib/one/datastores/118/119/mapper/disk.1
Thu Feb 13 13:51:17 2025 [Z0][VMM][I]: sudo -n bindfs --uid-offset=-9869 --gid-offset=-9869 -o suid /var/lib/one/datastores/118/119/mapper/disk.1 /var/lib/lxc-one/119/disk.1
Thu Feb 13 13:51:17 2025 [Z0][VMM][I]: sudo lxc-create -n ‘one-119’ --config /var/lib/one/datastores/118/119/deployment.file --template none
Thu Feb 13 13:51:17 2025 [Z0][VMM][I]: Error executing: sudo lxc-start -n ‘one-119’
Thu Feb 13 13:51:17 2025 [Z0][VMM][I]: [stderr]: lxc-start: one-119: lxccontainer.c: wait_on_daemonized_start: 851 Received container state “ABORTING” instead of “RUNNING”
Thu Feb 13 13:51:17 2025 [Z0][VMM][I]: lxc-start: one-119: tools/lxc_start.c: main: 329 The container failed to start
Thu Feb 13 13:51:17 2025 [Z0][VMM][I]: lxc-start: one-119: tools/lxc_start.c: main: 332 To get more details, run the container in foreground mode
Thu Feb 13 13:51:17 2025 [Z0][VMM][I]: lxc-start: one-119: tools/lxc_start.c: main: 335 Additional information can be obtained by setting the --logfile and --logpriority options
Thu Feb 13 13:51:17 2025 [Z0][VMM][I]: Check container logs at /var/log/lxc/one-119.log
Thu Feb 13 13:51:17 2025 [Z0][VMM][I]: deploy: No block device on /var/lib/one/datastores/118/119/mapper/disk.0
Thu Feb 13 13:51:17 2025 [Z0][VMM][I]: sudo -n umount /var/lib/lxc-one/119/disk.1
Thu Feb 13 13:51:17 2025 [Z0][VMM][I]: sudo -n umount /var/lib/one/datastores/118/119/mapper/disk.1
Thu Feb 13 13:51:17 2025 [Z0][VMM][I]: sudo -n losetup -d /dev/loop0
Thu Feb 13 13:51:17 2025 [Z0][VMM][I]: sudo lxc-ls
Thu Feb 13 13:51:17 2025 [Z0][VMM][I]: Error executing: sudo lxc-destroy -n ‘one-119’
Thu Feb 13 13:51:17 2025 [Z0][VMM][I]: [stderr]: lxc-destroy: one-119: utils.c: _recursive_rmdir: 162 Inappropriate ioctl for device - Failed to delete “/var/lib/lxc-one/119/disk.0”
Thu Feb 13 13:51:17 2025 [Z0][VMM][I]: lxc-destroy: one-119: storage/dir.c: dir_destroy: 133 Failed to delete “/var/lib/lxc-one/119/disk.0”
Thu Feb 13 13:51:17 2025 [Z0][VMM][I]: lxc-destroy: one-119: lxccontainer.c: container_destroy: 2984 Error destroying rootfs for one-119
Thu Feb 13 13:51:17 2025 [Z0][VMM][I]: lxc-destroy: one-119: tools/lxc_destroy.c: do_destroy: 129 Destroying one-119 failed
Thu Feb 13 13:51:17 2025 [Z0][VMM][I]: Check container logs at /var/log/lxc/one-119.log
Thu Feb 13 13:51:17 2025 [Z0][VMM][I]: There was an error starting the containter.
Thu Feb 13 13:51:17 2025 [Z0][VMM][I]: ExitCode: 255
Thu Feb 13 13:51:18 2025 [Z0][VMM][I]: ExitCode: 0
Thu Feb 13 13:51:18 2025 [Z0][VMM][I]: Successfully execute network driver operation: clean.
Thu Feb 13 13:51:18 2025 [Z0][VMM][I]: Failed to execute virtualization driver operation: deploy.
Thu Feb 13 13:51:18 2025 [Z0][VMM][E]: DEPLOY: INFO: deploy: No block device on /var/lib/one/datastores/118/119/mapper/disk.0 INFO: deploy: No block device on /var/lib/one/datastores/118/119/mapper/disk.1 sudo lxc-ls lsblk -o NAME,FSTYPE lsblk -o NAME,FSTYPE lsblk -o NAME,FSTYPE lsblk -o NAME,FSTYPE sudo -n mount /dev/vg-one-118/lv-one-119-0 /var/lib/one/datastores/118/119/mapper/disk.0 sudo -n bindfs --uid-offset=-9869 --gid-offset=-9869 -o suid /var/lib/one/datastores/118/119/mapper/disk.0 /var/lib/lxc-one/119/disk.0 sudo -n losetup --find --show /var/lib/one/datastores/118/119/disk.1 lsblk -o NAME,FSTYPE sudo -n mount /dev/loop0 /var/lib/one/datastores/118/119/mapper/disk.1 sudo -n bindfs --uid-offset=-9869 --gid-offset=-9869 -o suid /var/lib/one/datastores/118/119/mapper/disk.1 /var/lib/lxc-one/119/disk.1 sudo lxc-create -n ‘one-119’ --config /var/lib/one/datastores/118/119/deployment.file --template none Error executing: sudo lxc-start -n ‘one-119’ [stderr]: lxc-start: one-119: lxccontainer.c: wait_on_daemonized_start: 851 Received container state “ABORTING” instead of “RUNNING” lxc-start: one-119: tools/lxc_start.c: main: 329 The container failed to start lxc-start: one-119: tools/lxc_start.c: main: 332 To get more details, run the container in foreground mode lxc-start: one-119: tools/lxc_start.c: main: 335 Additional information can be obtained by setting the --logfile and --logpriority options Check container logs at /var/log/lxc/one-119.log INFO: deploy: No block device on /var/lib/one/datastores/118/119/mapper/disk.0 sudo -n umount /var/lib/lxc-one/119/disk.1 sudo -n umount /var/lib/one/datastores/118/119/mapper/disk.1 sudo -n losetup -d /dev/loop0 sudo lxc-ls Error executing: sudo lxc-destroy -n ‘one-119’ [stderr]: lxc-destroy: one-119: utils.c: _recursive_rmdir: 162 Inappropriate ioctl for device - Failed to delete “/var/lib/lxc-one/119/disk.0” lxc-destroy: one-119: storage/dir.c: dir_destroy: 133 Failed to delete “/var/lib/lxc-one/119/disk.0” lxc-destroy: one-119: lxccontainer.c: container_destroy: 2984 Error destroying rootfs for one-119 lxc-destroy: one-119: tools/lxc_destroy.c: do_destroy: 129 Destroying one-119 failed Check container logs at /var/log/lxc/one-119.log There was an error starting the containter. ExitCode: 255
Thu Feb 13 13:51:18 2025 [Z0][VM][I]: New LCM state is BOOT_FAILURE
Versions of the related components and OS (frontend, hypervisors, VMs):
Steps to reproduce:
Current results:
Expected results: