WilliamLam.com

Quick Tip - vSphere with Tanzu fails to sync Content Library with 500 Internal Server Error

by // Leave a Comment

While setting up a new vSphere with Tanzu environment (which can run with just 32GB of memory), I ran into a really strange issue where my vSphere Content Library templates were not being picked up by the VM Service. I was going insane as I have configured this a number of times and I have never ran into this particulare issue before. I thought maybe it was a configuration problem but the enablement of vSphere with Tanzu was 100% successful and everything was showing green.

While looking at the vmware-system-vmop-controller-manager container log, I noticed that the VM Service can see the template but it just fails to extract and process it and throws a 500 Internal Server Error message:

E0917 12:08:23.060929 1 content_library_provider.go:275] vsphere/contentlibrary "msg"="error extracting the OVF envelope from the library item" "error"="POST https://vcsa.tanzu.local:443/rest/com/vmware/content/library/item/download-session: 500 Internal Server Error" "contentLibraryUUID"="a298369b-7239-4b1c-988f-d361e5a001d6" "itemName"="ubuntu-22.04-custom-image"
E0917 12:08:23.060984 1 content_library_provider.go:275] vsphere/contentlibrary "msg"="error extracting the OVF envelope from the library item" "error"="POST https://vcsa.tanzu.local:443/rest/com/vmware/content/library/item/download-session: 500 Internal Server Error" "contentLibraryUUID"="1bfd8950-c846-46cf-bd50-55150a16bab3" "itemName"="photon-ova"
E0917 12:08:23.060998 1 contentsource_controller.go:203] controllers/ContentSource "msg"="failed to get VirtualMachineImage from content library" "error"="POST https://vcsa.tanzu.local:443/rest/com/vmware/content/library/item/download-session: 500 Internal Server Error" "clProviderName"="a298369b-7239-4b1c-988f-d361e5a001d6" "clProviderUUID"="a298369b-7239-4b1c-988f-d361e5a001d6"
E0917 12:08:23.061011 1 contentsource_controller.go:203] controllers/ContentSource "msg"="failed to get VirtualMachineImage from content library" "error"="POST https://vcsa.tanzu.local:443/rest/com/vmware/content/library/item/download-session: 500 Internal Server Error" "clProviderName"="1bfd8950-c846-46cf-bd50-55150a16bab3" "clProviderUUID"="1bfd8950-c846-46cf-bd50-55150a16bab3"
E0917 12:08:23.061032 1 contentsource_controller.go:401] controllers/ContentSource "msg"="Error in syncing image from the content provider" "error"="POST https://vcsa.tanzu.local:443/rest/com/vmware/content/library/item/download-session: 500 Internal Server Error" "name"="1bfd8950-c846-46cf-bd50-55150a16bab3"
E0917 12:08:23.061079 1 controller.go:317] controller/contentsource "msg"="Reconciler error" "error"="POST https://vcsa.tanzu.local:443/rest/com/vmware/content/library/item/download-session: 500 Internal Server Error" "name"="1bfd8950-c846-46cf-bd50-55150a16bab3" "namespace"="" "reconciler group"="vmoperator.vmware.com" "reconciler kind"="ContentSource"
E0917 12:08:23.061123 1 contentsource_controller.go:401] controllers/ContentSource "msg"="Error in syncing image from the content provider" "error"="POST https://vcsa.tanzu.local:443/rest/com/vmware/content/library/item/download-session: 500 Internal Server Error" "name"="a298369b-7239-4b1c-988f-d361e5a001d6"
E0917 12:08:23.061165 1 controller.go:317] controller/contentsource "msg"="Reconciler error" "error"="POST https://vcsa.tanzu.local:443/rest/com/vmware/content/library/item/download-session: 500 Internal Server Error" "name"="a298369b-7239-4b1c-988f-d361e5a001d6" "namespace"="" "reconciler group"="vmoperator.vmware.com" "reconciler kind"="ContentSource"

I was running out of ideas and things to try and I decided to look at the content library configuration to see if I had missed something.

[Read more...]

ESXi on Intel NUC 12 Pro (Wall Street Canyon)

by // 143 Comments

Many in the VMware Community, including myself, started with the classic 4x4 Intel NUC for running a VMware homelab. Over the years, this powerful little Intel NUC continues to enable a wide variety of new VMware use cases from running vSphere, vSAN, NSX, Tanzu and even vRealize (now Aria). It felt like it was just yesterday that I had switched from using an Apple Mac Mini to the latest Intel NUC (6th Generation) to build my new vSphere/vSAN Homelab, which was more than 6 years ago! ?

While Intel continues to expand and grow their "NUC" portfolio to include many other form factors, the classic 4x4 design still has a special place for many people in the VMware community. The classic Intel NUC is not only small, portable but also extremely capable, especially with last few releases which makes this an ideal kit for those just getting started with a new VMware Homelab.

If you are in the market for an upgrade this year, definitely check out the latest refresh of this classic 4x4 design with Intel's recent launch of the Intel NUC 12 Pro, formally known as the Wall Street Canyon NUC.

Let's take a closer look at this new Intel NUC 😀

[Read more...]

vSphere ESXi 7.x will be last version to officially support Apple macOS Virtualization

by // 11 Comments

As a heads up, I just wanted to share that VMware has just published a new knowledge base article to communicate that ESXi 7.x will be the last major release to officially support Apple macOS Virtualization, which was originally introduced back in 2011 with the release of vSphere 5.0.

Last year, VMware had also published a blog outlining that they will no longer pursue hardware certification for the Apple 2019 Mac Pro 7,1 for ESXi and as unfortunate as this is, hopefully this updated news will not come as a surprise to any of our customers or partners due to the various challenges in supporting the Apple hardware platform with ESXi.

On a more personal note, this is also a bitter sweet end, I have been writing about Apple macOS Virtualization on ESXi since its inception almost exactly 11 years ago. I came to learn about the new virtualization capability during an on-site beta for vSphere 5.0 (codenamed MN) at VMware HQ back when I was a customer. Not only did our organization have a need for this capability, but this was also the time that Apple had announced EOL'ed of Apple XServe, which was the initial hardware platform that was officially supported. I still recall emailing our leadership after the on-site to purchase as many XServe as we could before you could no longer buy the systems so that we can enable our development teams who were building both iOS and macOS applications.

It certainly has been a wild ride over the years in advocating for our users and their plethora of use cases to getting the Apple Mac Mini to run ESXi like any other x86 platform and even getting the Apple Mac Mini added to the VMware HCL. I still remember all the hoops and hacks that one needed to jump through just to boot ESXi and over the years, various VMware Engineers have incrementally helped get us to where we are at today, so a big thanks for all of their support over the years.