Good afternoon, I don’t know where to go and I really need help. I have tried many times to fix multiple errors with OneProvision when creating a cluster on AWS (virtual provision type). I have tried to do everything like in the video OpenNebula - Preventing Vendor Lock-in with an OpenNebula Multi-Cloud - YouTube . But the virtual machine does not appear to be successfully started in the VM partition on OpenNebula Sunstone. Also, during the automatic cluster configuration using the OneProvision built-in template, the Ansible “Unreachable” error occurs. Ansible “environmentfilter” error was previously found and fixed with difficulty, which was caused by a breakage in newer versions of Jinja2 starting with version 3.1.* (no information about this problem is available in the OpenNebula documentation and as far as I know, the problem is still not fixed in newer versions of the platform). Many other problems occur regardless of the choice of EC2 instance type, virtualization type (Ixc, gemu) and any other settings. In the video, everything is very easy and fast. However, in reality the cluster creation always fails (even if the status in OneProvision is green and shows as successful). Tested in Debian 11 and Ubuntu 20.04.
Also, searching the official OpenNebula documentation didn’t help. It gives vague explanations for this patch https://github.com/OpenNebula/docs/blob/master/source/quick_start/operation_basics/provisioning_edge_cluster.rst (“If you’re using OpenNebula 6.6.0 CE, before adding hosts to your environment, please apply this patch in all Frontend machines”).
The problem was similar to what was mentioned in another section of the documentation regarding Kubernetes Running Kubernetes Clusters — OpenNebula 6.6.3 documentation (“Important” message).
This problem is also relevant for any OneProvision cluster deployment on AWS (qemu, LXC) and is not explicitly mentioned in the documentation and Github.
The specialist believes that the problem is Terraform, which fails when using AWS with OneProvision. A new virtual machine is simply not created on Datastore aws-cluster-system. It always displays zero Capacity, regardless of how OpenNebula was configured. Will this very insidious bug be fixed in the future?
Versions of the related components and OS (frontend, hypervisors, VMs):
Baremetal (Host) OS – Ubuntu 22.04 (On Debian 11, the error is the same)
Frontend – 6.6.3
Steps to reproduce:
- Open the OneProvision interface.
- Add an AWS provider (IAM credentials with EC2FullAccess rights).
- Proceed to create a cluster (for example, in N. Virginia) with any options and resource types.
- Observe a “successful” cluster creation that fails with a green status.
- On OpenNebula Sunstone, observe that aws-cluster-system is zero capacity.
- Unsuccessfully try to create a virtual machine as shown in the third minute of the video.
Current results:
The virtual machine/container is not running on the AWS side.
Expected results:
The virtual machine/container is successfully started as shown in the video.