VM provisioning works Ubuntu 16.04 but fails with 18.04, 20.04 and 22.04

Provisioning & Self Service
,
1

Hello Experts, I have a urgent questions to ask regarding VMware cloud. I am trying to deploy various flavors or Ubuntu images. When I deploy VM with ‘Morpheus Ubuntu 16.04.6 v1’ image provided by Morpheus, it works as expected and I notice that size of template is 2.23GB. VM is assigned with IP address and I am able to access it normally.

image
image1087×294 31 KB

But When I tried to deploy Morpheus provided VMware templates for 18.04, 20.04 or 22.04, I noticed size of template is 1.83KB and I am not able to boot the VM.

image
image1094×298 30.6 KB

Am I missing something here. It is same thing with CentOS 7.5 images I am able to boot but other CentOS images like 8 and 9 having the same issues. Is there anything I need to take care while using old version templates vs new version of templates ?

2

Is the datastore out of space?

Are the esxi hosts resolvable from from Morpheus and have 443 open from Morpheus to connect and do an ovf import?

Are you using the images with build dates? Those are the most current images.

3

There is a lot of free space in datastore:

image
image1348×284 15.2 KB

I verified that ESXi hosts are reachable from Morpheus:
[root@morpheus-54-mgt ~]# ping 192.168.9.73
PING 192.168.9.73 (192.168.9.73) 56(84) bytes of data.
64 bytes from 192.168.9.73: icmp_seq=1 ttl=64 time=0.245 ms
64 bytes from 192.168.9.73: icmp_seq=2 ttl=64 time=0.242 ms
^C
— 192.168.9.73 ping statistics —
2 packets transmitted, 2 received, 0% packet loss, time 999ms
rtt min/avg/max/mdev = 0.242/0.243/0.245/0.015 ms
[root@morpheus-54-mgt ~]#

Also Morpheus is reachable from ESXi host:
[root@localhost:~] ping morpheus-54-mgt.helionit.io
PING morpheus-54-mgt.helionit.io (192.168.9.102): 56 data bytes
64 bytes from 192.168.9.102: icmp_seq=0 ttl=64 time=0.290 ms
64 bytes from 192.168.9.102: icmp_seq=1 ttl=64 time=0.366 ms

— morpheus-54-mgt.helionit.io ping statistics —
2 packets transmitted, 2 packets received, 0% packet loss
round-trip min/avg/max = 0.290/0.328/0.366 ms
[root@localhost:~]

I am simply selecting version of operating system not by build date and it works for 16.04 and doesn’t work for others:

image
image883×542 24.2 KB

4

Some of the following may help.

  • Try to curl to each of your esxi hosts from your Morpheus appliance
    curl -k https://192.168.9.x This should provide an html return

  • Delete the current partial download templates in your vCenter.

  • Provision another of the same type from Morpheus.

  • Check for the following task in vCenter (the status of this task may provide some info on why)

    image
    image908×35 4.7 KB

5

Thanks for support. Yes I did cleaned up all the images from vCenter and tried again, but still the same. 16.04 works and others does not work.

I am able to curl the ESXi hosts from Morpheus server:
[root@morpheus-54-mgt ~]# curl -k https://192.168.9.73

[root@morpheus-54-mgt ~]#
6

What does the task show in vCenter for the ovf deploy.

7

Its all completed without error, VM provision fails the same way:

image
image1564×804 86.6 KB

and here is the size of template, which shows 1.83KB:

image
image1871×719 92.6 KB

8

Hi @piyush.jain . You should’ve had an HTML return on the curl example Bob provided. This seems indicative of not having 443 connectivity from Morpheus to your ESXi host(s).

Something similar to this:

image
image732×171 5.66 KB

9

Its same only, Its just that I paste the html snippet it didn’t show it here in my last comment for some reason:

image
image945×220 25.3 KB

10

Deleting the template in the vcenter and retrying from Morpheus should result in logs both on Morpheus and vCenter. You should see references to OVF import and this would most likely show the error. If you’re still stuck afterwards, I would recommend raising a support ticket for better triaging.

11

I checked Morpheus logs, but couldn’t identify the reason, Is there a possibility you to check this once?
Google Drive Current Logs

12

@piyush.jain - Curious what version of vCenter and ESXi you are running? I do see the following in the log which may indicate a compatibility issue with the vCenter version the OVF was created from and the version you are running.

[Line 132: Unable to parse ‘flags.vvtdEnabled’ for attribute ‘key’ on element ‘Config’. , Line 133: Unable to parse ‘flags.vbsEnabled’ for attribute ‘key’ on element ‘Config’. ]

13

Thanks for looking into the logs and identify the issue. I would check with our lab team to also validate this at there end.
Here is the version we are using for vCenter and ESXi:
vCenter: 6.5.0, Build: 8815520
Hypervisor: VMware ESXi, 6.5.0, Build: 5146846

14

That looks to be the problem. Both vvtdEnabled and vbsEnabled dont look like exist until 6.7. Below is a reference from VMware on version support. With that being said 6.5 and 6.7 both went End of General Support on October 15th 2022. I would recommend either upgrading your environment to a currently supported version of vSphere or creating your own custom templates in vCenter and using those in Morpheus.

https://vdc-repo.vmware.com/vmwb-repository/dcr-public/1ef6c336-7bef-477d-b9bb-caa1767d7e30/82521f49-9d9a-42b7-b19b-9e6cd9b30db1/vim.vm.FlagInfo.html

For reference i am currently running vCenter 7 and have no issues using these templates.

15

Thanks a lot for support. Its really great.
We would plan to upgrade our environment and test this again.