VMware released a new vCenter Server version: 7.0.0b, 22.214.171.12400, build 16386292. In this article I cover the resolved issues and I show how easy is to update from the previous version of vCenter Server 7.0.0 to the latest 7.0.0b.
In case you are looking for an upgrade demonstration from vCenter Server 6.7 to vCenter Server 7.0.0, you can check my other article: How to Upgrade vCenter Server Appliance from 6.7 to 7.0 – Stage 1.
If you want to install vCenter 7.0.0, please check How to Install VMware vSphere 7.0.
vCenter Server 7.0.0b – Resolved Issues
vCenter Server 7.0.0b introduces two new features:
- It adds a Replication State Change alarm to the vCenter Server Appliance that displays when a replication state changes to READ_ONLY.
- You can use the Show only rollup updates toggle button to filter and select patches that you want to include in a baseline when using the vSphere Lifecycle Manager.
This release of vCenter Server delivers the following patch:
vCenter Server 7.0.0b resolves the following issues:
- Security updates (SQLite database 3.31.1, dom4j library 2.1.3, libxml2 library 2.9.10, Apache Tomcat 8.5.51, cURL 7.69.1, Python 3.5.9, Freetype Python 2.9, Postgres 11.7, OpenJDK 126.96.36.199, Eclipse Jetty 9.4.26)
- Migrating or cloning encrypted virtual machines across vCenter Server instances fails when attempting to do so by using the vSphere Client
- Auto Deploy – Creating an image profile might fail with an error Invalid Fault: ThrowableProxy.cause ‘name’
- Patching witness or passive nodes of environments with VMware vCenter Server High Availability enabled might fail
- Upgrading to vCenter Server 7.0 fails with the message that an error has occurred while starting service ‘sps’
- A VMware vSphere with Kubernetes cluster might stay long in a configuring state after a vCenter Server upgrade
- You cannot open the vCenter Server Appliance installer app in Linux virtual machines by double-clicking it
- You can still see Updates Available in the Summary tab of the vSphere Client after updating your vCenter Server system (this is the issue I reported when upgrading from vCenter 7.0.0 to 7.0.0a).
- If the vCenter Single Sign-On or machine SSL certificate of a vCenter Server machine contain a mix of uppercase and lowercase characters, migration or upgrade prechecks fail
- If multiple DNS entries exist in a vCenter Single Sign-On or machine SSL certificate of a vCenter Server machine, and the Common Name (CN) does not match the vCenter Server PNID, migration and upgrade prechecks fail
- The VM storage compliance monitoring service might not trigger recomputation of compliance status
- vCenter Server does not report compatible datastores when datastores are mounted on multiple data centers
- The third level of nested objects in a virtual machine folder is not visible
- Migration of virtual machines between vCenter Server instances fails with an error
- In VMware Cloud Director, uploading customization packages to a vApp might not succeed due to failure to acquire a generic service ticket
- Container Storage Interface (CSI) external provisioner fails to provision a PersistentVolumeClaim (PVC) in a vCenter Server testbed that uses a custom HTTPS port
- The Container Storage Interface (CSI) migration feature might be disabled by default
- When you have enabled VMware vSphere High Availability in a vSAN cluster that uses different subnets for traffic, timeouts in the networking layer cause incorrect vSphere HA status of some ESXi hosts
- Current Memory Failover Capacity metric displays above 100%
How to Update to vCenter Server 7.0.0b
Go to the appliance management console (https://<vCSA-FQDN>:5480/ – in my case that will be https://vcenter.cloudhat.local:5480/) and login using the root appliance password. Navigate to Update menu. We can see current version is 188.8.131.5200 and we have an available update to 184.108.40.20600 (which is vCenter Server 7.0.0b). Click on “Stage and install” link.
From now on, it is a pretty standard vCenter Server upgrade. Accept End user license agreement and click “Next”.
Choose if you want to join Customer Experience Improvement Program. Make your choice and click “Next”.
Next wizard section asks us to confirm we took a backup of the current vCenter. Click “Finish” when done with the backup.
The installation process starts now.
After going through more installation stages, the vCenter services will get started and the installation will be complete.
Reloading the vCenter Server appliance management console, we see now the new build, 16386292.