Please, describe the problem here and provide additional information below (if applicable) …
We are trying to deploy OpenNebula on our corporate Red Hat Virtualization using VMs and based on LXD, but we cannot instantiate containers from Marketplace.
-Platform: Red Hat Virtualization
* hypervisors: Red Hat Enterprise Linux release 7.4
* manager: Red Hat Virtualization Manager Version: 4.1
-Test environment: 1 OpenNebula frontend VM + 1 OpenNebula host VM
Versions of the related components and OS (frontend, hypervisors, VMs):
- Red Hat Virtualization’s VMs installed using default parameters (apart from disks, nics etc…)
- OS frontend and host: ubuntu 18.04
- OpenNebula: 5.8.1
- OpenNebula hypervisor: LXD
Steps to reproduce:
- downloaded ‘ubuntu_xenial - LXD’ from MarketPlace
- Instantiated a container based on ‘ubuntu_xenial - LXD’ template
- Status. FAILURE
Note: the same results apply for any apps
Current results:
- Log copied from browser ‘Log’ tab (sunstone):
Tue Jun 11 10:40:32 2019 [Z0][VM][I]: New state is ACTIVE
Tue Jun 11 10:40:32 2019 [Z0][VM][I]: New LCM state is PROLOG
Tue Jun 11 10:40:39 2019 [Z0][VM][I]: New LCM state is BOOT
Tue Jun 11 10:40:39 2019 [Z0][VMM][I]: Generating deployment file: /var/lib/one/vms/25/deployment.0
Tue Jun 11 10:43:10 2019 [Z0][VMM][I]: Successfully execute transfer manager driver operation: tm_context.
Tue Jun 11 10:43:10 2019 [Z0][VMM][I]: Successfully execute network driver operation: pre.
Tue Jun 11 10:43:17 2019 [Z0][VMM][I]: Command execution fail: cat << EOT | /var/tmp/one/vmm/lxd/deploy '/var/lib/one//datastores/0/25/deployment.0' 'host1' 25 host1
Tue Jun 11 10:43:17 2019 [Z0][VMM][I]: deploy: Using raw filesystem mapper for /var/lib/one/datastores/0/25/disk.0
Tue Jun 11 10:43:17 2019 [Z0][VMM][I]: deploy: Mapping disk at /var/lib/lxd/storage-pools/default/containers/one-25/rootfs using device /dev/loop14
Tue Jun 11 10:43:17 2019 [Z0][VMM][I]: deploy: Mounting /dev/loop14 at /var/lib/lxd/storage-pools/default/containers/one-25/rootfs
Tue Jun 11 10:43:17 2019 [Z0][VMM][I]: deploy: Mapping disk at /var/lib/one/datastores/0/25/mapper/disk.1 using device /dev/loop28
Tue Jun 11 10:43:17 2019 [Z0][VMM][I]: deploy: Mounting /dev/loop28 at /var/lib/one/datastores/0/25/mapper/disk.1
Tue Jun 11 10:43:17 2019 [Z0][VMM][I]: deploy: Name: one-25
Tue Jun 11 10:43:17 2019 [Z0][VMM][I]: Remote: unix://
Tue Jun 11 10:43:17 2019 [Z0][VMM][I]: Architecture: x86_64
Tue Jun 11 10:43:17 2019 [Z0][VMM][I]: Created: 2019/06/11 08:43 UTC
Tue Jun 11 10:43:17 2019 [Z0][VMM][I]: Status: Stopped
Tue Jun 11 10:43:17 2019 [Z0][VMM][I]: Type: persistent
Tue Jun 11 10:43:17 2019 [Z0][VMM][I]: Profiles: default
Tue Jun 11 10:43:17 2019 [Z0][VMM][I]:
Tue Jun 11 10:43:17 2019 [Z0][VMM][I]: Log:
Tue Jun 11 10:43:17 2019 [Z0][VMM][I]:
Tue Jun 11 10:43:17 2019 [Z0][VMM][I]: lxc one-25 20190611084314.867 WARN conf - conf.c:lxc_setup_devpts:1616 - Invalid argument - Failed to unmount old devpts instance
Tue Jun 11 10:43:17 2019 [Z0][VMM][I]: lxc one-25 20190611084314.896 ERROR start - start.c:start:2028 - No such file or directory - Failed to exec "/sbin/init"
Tue Jun 11 10:43:17 2019 [Z0][VMM][I]: lxc one-25 20190611084314.896 ERROR sync - sync.c:__sync_wait:62 - An error occurred in another process (expected sequence number 7)
Tue Jun 11 10:43:17 2019 [Z0][VMM][I]: lxc one-25 20190611084314.896 ERROR lxccontainer - lxccontainer.c:wait_on_daemonized_start:842 - Received container state "ABORTING" instead of "RUNNING"
Tue Jun 11 10:43:17 2019 [Z0][VMM][I]: lxc one-25 20190611084314.897 ERROR start - start.c:__lxc_start:1939 - Failed to spawn container "one-25"
Tue Jun 11 10:43:17 2019 [Z0][VMM][I]: lxc 20190611084314.898 WARN commands - commands.c:lxc_cmd_rsp_recv:132 - Connection reset by peer - Failed to receive response for command "get_state"
Tue Jun 11 10:43:17 2019 [Z0][VMM][I]:
Tue Jun 11 10:43:17 2019 [Z0][VMM][I]: deploy: Using raw filesystem mapper for /var/lib/one/datastores/0/25/disk.0
Tue Jun 11 10:43:17 2019 [Z0][VMM][I]: deploy: Unmapping disk at /var/lib/lxd/storage-pools/default/containers/one-25/rootfs
Tue Jun 11 10:43:17 2019 [Z0][VMM][I]: deploy: Umounting disk mapped at /dev/loop14
Tue Jun 11 10:43:17 2019 [Z0][VMM][I]: deploy: Unmapping disk at /var/lib/one/datastores/0/25/mapper/disk.1
Tue Jun 11 10:43:17 2019 [Z0][VMM][I]: deploy: Umounting disk mapped at /dev/loop28
Tue Jun 11 10:43:17 2019 [Z0][VMM][I]: /var/tmp/one/vmm/lxd/client.rb:101:in `wait': {"type"=>"sync", "status"=>"Success", "status_code"=>200, "operation"=>"", "error_code"=>0, "error"=>"", "metadata"=>{"id"=>"43589008-a585-4775-9c58-75750c9acf53", "class"=>"task", "description"=>"Starting container", "created_at"=>"2019-06-11T10:43:14.615529499+02:00", "updated_at"=>"2019-06-11T10:43:14.615529499+02:00", "status"=>"Failure", "status_code"=>400, "resources"=>{"containers"=>["/1.0/containers/one-25"]}, "metadata"=>nil, "may_cancel"=>false, "err"=>"Failed to run: /usr/lib/lxd/lxd forkstart one-25 /var/lib/lxd/containers /var/log/lxd/one-25/lxc.conf: "}} (LXDError)
Tue Jun 11 10:43:17 2019 [Z0][VMM][I]: from /var/tmp/one/vmm/lxd/container.rb:429:in `wait?'
Tue Jun 11 10:43:17 2019 [Z0][VMM][I]: from /var/tmp/one/vmm/lxd/container.rb:441:in `change_state'
Tue Jun 11 10:43:17 2019 [Z0][VMM][I]: from /var/tmp/one/vmm/lxd/container.rb:184:in `start'
Tue Jun 11 10:43:17 2019 [Z0][VMM][I]: from /var/tmp/one/vmm/lxd/deploy:75:in `<main>'
Tue Jun 11 10:43:17 2019 [Z0][VMM][I]: ExitCode: 1
Tue Jun 11 10:43:17 2019 [Z0][VMM][I]: Failed to execute virtualization driver operation: deploy.
Tue Jun 11 10:43:17 2019 [Z0][VMM][E]: Error deploying virtual machine
Tue Jun 11 10:43:17 2019 [Z0][VM][I]: New LCM state is BOOT_FAILURE
- lxc log (/var/log/lxd/one-25/lxc.log):
lxc one-25 20190611084314.867 WARN conf - conf.c:lxc_setup_devpts:1616 - Invalid argument - Failed to unmount old devpts instance
lxc one-25 20190611084314.896 ERROR start - start.c:start:2028 - No such file or directory - Failed to exec "/sbin/init"
lxc one-25 20190611084314.896 ERROR sync - sync.c:__sync_wait:62 - An error occurred in another process (expected sequence number 7)
lxc one-25 20190611084314.896 ERROR lxccontainer - lxccontainer.c:wait_on_daemonized_start:842 - Received container state "ABORTING" instead of "RUNNING"
lxc one-25 20190611084314.897 ERROR start - start.c:__lxc_start:1939 - Failed to spawn container "one-25"
lxc 20190611084314.898 WARN commands - commands.c:lxc_cmd_rsp_recv:132 - Connection reset by peer - Failed to receive response for command "get_state"
- /var/log/lxd/one-25/{console,forkstart}.log are emtpy
Expected results:
On my personal environment based on “VirtualBox 6” with the same configuration, all containers are instantiated successfully in the ‘RUNNING’ state.
So we would like to know if RedHat VMs (based on kvm) are compatible or need some tweaking of creation’s parameter or what else?
Thanks