WilliamLam.com

Stage Only & Stage and Install buttons disabled when updating to vSphere 7.0 Update 2a 

by // 3 Comments

vSphere 7.0 Update 2a was just released yesterday and it introduces the highly anticipated vSphere Virtual Machine Service which is part of the vSphere with Tanzu solution. Customers will now be able to get the exact same Kubernetes-native provisioning and management experience for deploying Virtual Machine based workloads along side their Kubernetes-based applications.

I was definitely interested in checking out this new feature and quickly navigated to my VCSA to start the upgrade and to my surprise, I noticed that both the Stage Only and Stage and Install buttons were disabled (grayed out) and preventing me from updating to the latest release!


I had filed an issue internally and after some troubleshooting, it looks like this may have been remnants caused by the previous Exception occurred in install precheck phase issue, which I had ran into during the update to 7.0 Update 2. Although I was initially pointed by Engineering to VMware KB 83145, it did not resolve the issue and I ran into a couple more errors like "Previous patching unsuccessful" and "Downloading RPM …." messages within the VAMI UI as shown in the screenshots below

[Read more…]

2021 VMUG Advantage Community Group Buy

by // 1 Comment

Last year, I partnered up with the VMware User Group (VMUG) organization and shared with the VMware Community a special VMUG Advantage Homelab Group Buy offering, a first of its kind and it was a huge success! In fact, I still get pinged on a regular basis about the previous group buy and whether there would be another group buy?

Today, I am pleased to announce that both myself and Duncan Epping have teamed up with the VMUG organization to bring to the VMware Community the 2021 VMUG Advantage Group Buy!

For those not familiar with the VMUG Advantage membership, it provides benefits such as access to training, VMworld discounts but also to EVALExperience, which provides you with 365-days access (non-production usage) to the latest VMware solutions such as vSphere, vSAN, NSX, vRealize Suite and VMware Cloud Foundation. The EVALExperience alone is worth the normal $200 USD membership fee and is certainly one of the cheapest and easiest way to get access to all the latest VMware offerings for homelab and educational purposes.

The table below provides the respective discounts based on the quantity of VMUG Advantage membership purchases. The larger the interests group, the larger the discount.

[Read more…]

Why does Deploy OVF Template operation show vpxd-extension-[uuid]?

by // Leave a Comment

A question that I had received awhile ago from a customer was how to identify the specific user(s) who have deployed an OVF/OVA? Customers can easily do this by leveraging vCenter Serve Events, which are extremely rich with information that can help answer this and many other questions you might have in your vSphere enviornment.


The first challenge that you will find is that an OVF/OVA import operation is mapped to a generic vCenter TaskEvent, which will require some additional filtering. Secondly, depending on the method that was used to deploy the OVF/OVA such as the vSphere UI or using Automation tools like OVFTool or PowerCLI, you will also slightly diffrent behaviors in terms of the vCenter Server Events that are emitted.

If you deploy an OVF/OVA using the vSphere UI, you may have noticed there are actually two vCenter tasks which are displayed and running simultaneously as shown in the screenshot above. The first task is called "Import OVF package" and you will see that this task is associated with the actual user who initiated the import. The second task called "Deploy OVF template" is then associated with a vCenter system account that handles the actual deployment which will show up with a vpxd-extension-[uuid] username. This occurs because the user who is performing the import is not interacting directly with with vCenter Server, but rather through the vSphere UI which uses a system account to then communicate the operation to vCenter Server.

For this reason, when an OVF/OVA is imported through the vSphere UI, you will need to look at the TaskEvent and filter for the initial import operation. If an OVF/OVA is imported using the vSphere API using something like OVFTool, PowerCLI or any other vSphere SDK, then you will only see the Deploy OVF Template operation and the user associated with that operation is the person who initiated the import.

Using PowerCLI and the Get-VIEvent cmdlet, we can easily filter out these two types of TaskEvents.

Get-VIEvent | where {$_.GetType().Name -eq "TaskEvent" -and $_.FullFormattedMessage -eq "Task: Import OVF package"}

Get-VIEvent | where {$_.GetType().Name -eq "TaskEvent" -and $_.FullFormattedMessage -eq "Task: Import OVF package"}