/New vCenter 7 Update 3b how to update – now removed by VMware

New vCenter 7 Update 3b how to update – now removed by VMware


— Important note: Incredible that I have published this blog post that I had written a couple of days ago and did some changes to publish and after publishing I check the vCenter 7 Update 3b Release Notes doesn’t exist anymore.

According to KB86191 the patch and also the ISO version was removed from VMware because had some issues with HA(vSphere HA fails to enable). This is exactly what I had before and had discussed in my previous blog post about this vSphere 7 updates.

Honestly, I don’t know what to say more about VMware updates and these continuous issues that are not been properly tested. Don’t they test this properly before they launch the updates or the patches?

Since the post is about how to apply a patch, 3b or other, I will leave the blog post published anyway and will update and VMware fix again and launch the proper patch with no issues. We hope.

But in the main vCenter had no issues for now. But it could be because I already did the workaround that I discussed in HERE and fix the issue that was wrong with the i46enu vib and they do not exist anymore in the ESXi hosts.

UPDATE 20/11/2021: VMware is announced that it will completely remove from their Download portal any vCenter/vSphere 7 Update 3b. At the moment only vCenter/vSphere 7 Update 3a is available.

VMware official Information

Some, complement informational answers KB86398

End Note —

The vCenter update that we were waiting to fix some of the issues from previous versions is finally out. In this blog, New vCenter 7 Update 3b how to update, I will explain what is new, what is fixed in this version, and how to update your vCenter 7 since we need to do it manually when you have a previous version.

With this new vCenter 7 update 3b there is also new ESXi 7 update 3b patches. But if you try to stage, remediate any of your ESXi with these three new updates before updating your vCenter, it is not possible. You will get errors in the stage or when you try to remediate.

What are the main issues that this patch will address and fix?

  • Upgrade to ESXi 7.0 Update 3 might fail due to changed name of the inbox i40enu network driver.
  • You cannot enable vSphere HA on ESXi 7.0 Update 3 hosts.
  • Rollup update by using a patch baseline to ESXi 7.0 Update 3 might fail.
  • The hostd service might fail due to a time service event monitoring issue.

Some of the above issues I have already talked about in this blog, in HERE.

How to download and install the patch

Login to your VMware account and go to VMware Patch Portal

Select VC and 7.0.3 and click Search, then you would see the patch vCenter 7 update 3b. Click download and download the file VMware-vCenter-Server-Appliance-7.0.3.00200-18901211-patch-FP.iso

New vCenter 7 Update 3b how to update

As you can notice, this is a patch file, not an ISO to upgrade. So to apply this type of file, we need to do it manually.

How to apply the patch.

First, you need to import the ISO to one of your ESXi datastores.

New vCenter 7 Update 3b how to update

Then you can put the ISO in the vCenter Virtual CD/DVD drive and enable Connected and Boot At Power On(if you boot your vCenter before applying the patch).

New vCenter 7 Update 3b how to update

Note: For some reason, when I try the above, I always get an error, and it was not possible to enable the ISO on vCenter. I needed to power off vCenter, login to the ESXi where vCenter VM was running, add the ISO again, enable, and power on.

So if you have the same issue, you need to do this with the vCenter power off, and of course, you need to it in the ESXi that the vCenter VM is running.

After the ISO is set on vCenter VM, we can start the update process.

Second, you need to login into your VCSA console(not the shell Linux line command).

If you log in and are automatically in the VCSA Linux shell, you need to change the chsh bash for the application. Run the following command chsh -s /bin/appliancesh root

Exit and login, and you will now be the VCSA Console. Do not use the command shell to go again to the VCSA Linux shell, the patch needs to run in the VCSA Console.

Example:

In the VCSA, we need to use three commands:

  • software-packages stage -–iso
  • software-packages list -–staged
  • software-packages install –staged

Stage

First, we need to stage the ISO in vCenter.

List Stage files

Install Patch

After the ISO file is staged and all is ok, we can now install the patch.

This last step will take a while, but after you see the Installation process is completed successfully, your patch has been installed correctly.

We now have a vCenter 7 update 3b

I thought all was ok when I noticed a warning in the VM Console, a vCenter warning the following message: “vmdir.password is not set; aborting installation”

New vCenter 7 Update 3b how to update

I remember this error from previous versions, but old ones. I never had this, but I remember to read something about it.

This happened when the update/patch did not finish correctly. But looking at my /var/log/firstboot/rpmInstall.json file, I see success, so all should be ok.

I tested vCenter all seemed to work fine, but the warning was still there. So I followed the KB84259 to remove the warning and Rebooted, and the warning was gone.

Then I could update all the ESXi hosts with the new vSphere 7 update 3b without any issues.

Final notes:

Finally, VMware launched this patch to fix some of the issues we had from update 2 and update 3a. The HA issue had a significant impact on some of our vCenters/Clusters.

Since vSphere 7/vCenter 7 was launched, we have had so many issues that I can’t remember an ESXi version with so many bad bugs and significantly impacted VMware infrastructure. Like I already discussed HERE and HERE.

I hope now we have stable vCenter and ESXi hosts. We have been doing workarounds, fixes, updates, etc., since August. For companies with hundreds of ESXi hosts and thousands of VMs, this has a considerable impact and means many, many man-hours to handle all these issues.

Share this article if you think it is worth sharing. If you have any questions or comments, comment here, or contact me on Twitter.

©2021 ProVirtualzone. All Rights Reserved
By | 2021-11-21T12:47:29+01:00 November 18th, 2021|VMware, vSphere|2 Comments

About the Author:

I am over 20 years’ experience in the IT industry. Working with Virtualization for more than 10 years (mainly VMware). I am an MCP, VCP6.5-DCV, VMware vSAN Specialist, Veeam Vanguard 2018/2019, vExpert vSAN 2018/2019 and vExpert for the last 4 years. Specialties are Virtualization, Storage, and Virtual Backups. I am working for Elits a Swedish consulting company and allocated to a Swedish multinational networking and telecommunications company as a Teach Lead and acting as a Senior ICT Infrastructure Engineer. I am a blogger and owner of the blog ProVirtualzone.com

2 Comments

    • Luciano Patrao 21/11/2021 at 12:36 - Reply

      Notice today when I read the email sent by VMware. Honestly don’t know what to say 🙁

Leave a Reply

%d bloggers like this: