VMware Data Services Manager 2.1.3 Release Notes

VMware Data Services Manager 2.1.3 \| 16 OCT 2024 \| Build 24338851 Check for additions and updates to these release notes.

VMware Data Services Manager 2.1.3 | 16 OCT 2024 | Build 24338851

Check for additions and updates to these release notes.

What's New

VMware Data Services Manager 2.1.3 provides the following capabilities:

Support for special characters in naming VM folders nested last in the root VM folder of a vCenter datacenter
VMware Data Services Manager users can now use the special characters [] and the space symbol when naming Infrastructure Policy target VM folders nested last in the root VM folder of a vCenter datacenter.

Notes:
- Before you upgrade to VMware Data Services Manager 2.1.3, delete the Infrastructure Policy created with the nested VM folders and delete any database clusters that were stuck due to the You cannot provision database clusters using an Infrastructure Policy with a VM folder that contains special characters known issue documented in the VMware Data Services Manager 2.1.2 release notes.
- Do not use the special characters [] when you name the parent or ancestor VM Folders.
Postgres Host-Based Authentication Configuration API

VMware Data Services Manager users can now configure authentication options in pg_hba.conf for Postgres. This enhancement allows more flexibility in configuring custom users and other authentication methods. The feature is exposed through a new Postgres Cluster Custom Resource API. For additional information about VMware Data Services Manager 2.1.X APIs, see the Broadcom Developer Portal page.
Various bug fixes

Supported Platforms

The following table identifies the supported component versions for VMware Data Services Manager version 2.1.3.

Note:

Make sure to activate vSphere HA and vSphere DRS on the vSphere clusters that you use for the infrastructure policies. For information, see How vSphere HA Works in vSphere Availability and Create a vSphere DRS Cluster in vSphere Resource Management.

Component	Supported Versions
vCenter	7.0.3i and later
ESXi	7.0 and later
VMFS	5 and 6
PostgreSQL	16.4, 15.8, 14.13, 13.16, 12.20
MySQL	8.0.34, 8.0.32, 8.0.31, 8.0.29

Component Versions

The VMware Data Services Manager 2.1.3 release includes the following software component versions:

Component	Version
antrea	v1.13.3_vmware.1
cert-manager-cainjector	v1.12.2_vmware.2
cert-manager-controller	v1.12.2_vmware.2
cert-manager-webhook	v1.12.2_vmware.2
cloud-provider-vsphere	v1.28.0_vmware.1
coredns	v1.10.1_vmware.17
csi-attacher	v4.5.0_vmware.1
csi-livenessprobe	v2.12.0_vmware.1
csi-node-driver-registrar	v2.10.0_vmware.1
csi-provisioner	v4.0.0_vmware.1
csi-snapshotter	v7.0.1_vmware.1
dsm-alloydb-instance	2.1.0-20240618T1153Z-87da465c
dsm-alloydb-operator	2.1.0-20240618T1153Z-87da465c
etcd	v3.5.11_vmware.4
fluent-bit	v2.1.6_vmware.1
kapp	v0.48.2_vmware.1
kube-apiserver	v1.28.7_vmware.1
kube-controller-manager	v1.28.7_vmware.1
kube-proxy	v1.28.7_vmware.1
kube-scheduler	v1.28.7_vmware.1
kube-vip	v0.5.7_vmware.2
kubernetes-csi_external-resizer	v1.10.0_vmware.1
Kubernetes node OS	ubuntu 22.04
mysql-operator	2.1.1-20240804T2127Z-45c4ca2a
pause	3.9
postgres-operator	2.1.1-20240812T1050Z-daf4a9f7
telegraf	1.29.0
telegraf-chart	1.1.2
volume-metadata-syncer	v3.3.1_vmware.1
vsphere-block-csi-driver	v3.3.1_vmware.1

Resolved Issues

The 2.1.3 release of VMware Data Services Manager resolves the following known issues that appeared in the previous releases.

To find detailed descriptions and workarounds of these issues, search the VMware Data Services Manager 2.1.2 Release Notes.

You cannot provision a database cluster using an Infrastructure Policy with a VM folder nested under another folder in the root VM folder of a vCenter datacenter

Known Issues

Updated - You cannot provision database clusters using an Infrastructure Policy with a VM folder that contains special characters

When you try to provision a database cluster using an Infrastructure Policy with a VM folder that contains special characters like * ? \ in its name, the database cluster never achieves status Ready and the VMs for this cluster are never created in the vSphere inventory tree.

Workaround: Do not use special characters like * ? \ in the name of the folder selected in the Infrastructure Policy.
Postgres HA database gets permanent alerts after you apply a custom certificate

After you apply a custom certificate without the X509v3 extension KeyUsage DigitalSignature to a Postgres HA instance, the database starts to get permanent alerts.

Workaround: Restore or clone to another database, using a certificate with the X509v3 extension KeyUsage DigitalSignature.
MySQL database cluster remains In Progress indefinitely after you deactivate the Directory Service

If you deactivate the Directory Service, this causes the MySQL database cluster and its Modify Database Cluster task to become stuck.

Workaround: None.
You cannot save SMTP configuration settings with a self-signed certificate

When you try to save an SMTP configuration with a self-signed certificate, you are prompted to accept the certificate, but after you click Accept, the dialog might remain open, not allowing you to proceed and click Save.

Workaround: Refresh the Settings page by clicking the Refresh Details button in the top-right corner of the page, then click Save.
You cannot create databases that use a storage policy with encryption after upgrading from VMware Data Services Manager version 2.1 to 2.1.1.

When you try to provision a database that uses a storage policy with encryption after upgrading from VMware Data Services Manager version 2.1 to 2.1.1, the process fails. VM encryption is available with vSphere 8.0 Update 3 and VMware Cloud Foundation 5.2. The issue is caused by missing privileges to the DSM Administrator role in vCenter.
Workaround: In vCenter, edit the DSM Administrator role by adding the following privileges under Cryptographic operations:
- Add disk
- Clone
- Encrypt
- Encrypt new
- Migrate
- Register VM
See Using vCenter Server Roles to Assign Privileges in the VMware vSphere Product Documentation.
You cannot log in to VMware Data Services Manager using LDAP credentials after upgrading from version 2.0.3 to 2.1

Upgrading VMware Data Services Manger from version 2.0.3 to 2.1 might cause a reset of the LDAP settings and as a result users are unable to log in to VMware Data Services Manager using LDAP credentials. In some cases VMware Data Services Manger cannot find the leaf (or root) certificate of the LDAP server which might lead to errors in migration. You might see the following or a similar error message:

<YYY-MM-DD> <HH:mm:ss.SSS> ERROR [main] .s.PostUpgradeProcessorService - Exception fetching cert by url, skipping DirectoryService migration com.vmware.tdm.sp.common.exception.TdmException: Certificate for the server ldaps://example_ldap_host:636 should be self-signed or issuer CA certificate should be added to the Trusted Root Certificates.
Workaround: Add the root certificates again and reconfigure the directory service.
1. Log in to the VMware Data Services Manager UI using a locally created user.
  
  If you need to create a local user, use the VMware Data Services Manager plug-in in vCenter.
2. To add the certificates, navigate to Settings > Trusted Root Certificates > Add.
3. To reconfigure the directory service, navigate to Directory Service Settings > Configure Directory Service.
4. Validate log in to VMware Data Services Manager UI using LDAP credentials.
The VMware Data Services Manager user interface does not load after upgrading to version 2.1

After you successfully upgrade VMware Data Services Manager to version 2.1 and then enter your credentials, the user interface is stuck in a loading screen. This issue is caused by a network interruption between AWS and VMware Data Services Manager during the bundle download process from the provider repository.
Workaround:
1. Establish an SSH connection to the VMware Data Services Manager appliance.
2. Extract the bearer token by running the following command:
  
  curl -k -v -location 'https:/<provider_ip>/provider/session' --header 'Content-Type: application/json' --data-raw '{ "email" : "YourEmailAddress", "password" : "YourPassword" }'
3. Copy the files from S3 to the local appliance by executing the following command:
  
  curl -k -v --location --request POST 'https://<PROVIDER_IP_ADDRESS>/updatemanager/copy-bundles' \--header 'Authorization: Bearer <BEARER TOKEN>' \--header 'Accept: application/json, text/plain, */*'
  
  The copying process might take between 1 and 2 hours.
After an upgrade to DSM version 2.1, the vSphere Client shows the DSM version as 2.0.3
You can see version 2.0.3 on the following pages of the vSphere Client:
- In vCenter DSM plugin, click Configure > Version & Upgrade.
  
  You can observe that Current Control Plane Version in the Version Information pane displays version 2.0.3.
- In vCenter, click Administration > Client Plugins > Data Service Manager Plugin.
  
  Observe that the Instance version column shows 2.0.3.
Workaround:
1. Make sure that the DSM version shows correctly in the DSM console.
  1. In the DSM console, select Version & Upgrade from the left navigation pane, and click the DSM System tab.
  2. Check that Current Control Plane Version in the Version Information pane displays 2.1.0.XXXX.
2. Unregister and re-register the DSM plugin manually. See Unregistration and Re-registration of VMware Data Services Manager Plugin.
High CPU utilization on vSphere clusters running DSM databases might impact the ability to create, scale, or upgrade the databases

When DSM databases are running on vSphere clusters that are using large amounts of CPU, some database management operations my be impacted. This is especially true when high CPU alarm conditions have been raised on the vSphere clusters.

Workaround: Address the high CPU alarm condition raised on the vSphere cluster by adding more resources or migrating VMs to another vSphere cluster.
After a fresh installation of DSM 2.1, data services are not showing up in the Data Services tab of Version & Upgrade

If you navigate to the Data Services tab of the Version & Upgrade page in the DSM console, you cannot see available data services listed on the tab.
Workaround:
1. In the DSM console, select Version & Upgrade from the left navigation pane, and click the DSM System tab.
2. Click CHECK FOR UPGRADE in the Available Upgrades & History pane.
3. Wait two or three minutes for the data services to appear in the Data Services tab.
During a MySQL database cluster creation, a replica might occasionally fails to join the cluster
In addition, you might observe the following issues.

The bootstrapping process keeps failing and restarting repeatedly. The cluster fails to start.

You can also see the following error message:
```
❯ kubectl get mysqlcluster st1s-myreuse-001 -o yaml    
    ....
    message: 'Database is accessible, but 0 member/s is/are not online or not active
      members of the cluster: . No failure tolerance: Cluster is NOT tolerant to any
      failures.'
    observedGeneration: 1
    reason: Degraded
    status: "True"
    type: DatabaseEngineReady
```
Workaround: If the problem continues for over 30 minutes, delete the cluster and create it again.
VMware Data Services Manager 2.1 does not support five-node topology (3 replicas) for PostgreSQL database clusters

Only clusters with three nodes (1 replica) or a single node (0 replicas) are supported by VMware Data Services Manager 2.1.

Workaround: If you have any existing five-node clusters in your environment created with VMware Data Services Manager 2.0.3, they will continue to be functional after upgrading to 2.1, but you cannot edit them. You can clone or restore your five-node clusters into one-node (0 replicas) or three-node (1 replica) clusters if you want them to be modifiable in 2.1.
Performing scale operations on a database cluster, such as changing a VM class from small to medium or upgrading a database cluster, might cause failures if underlying ESXi hosts have active CPU or memory alarms

These alarms might indicate that the host does not have enough resources for workload cluster nodes.

Workaround: Make sure to address these alarms before performing scale operations.