DSM Upgrade from 2.2.1 to 2.2.3 may fail.

Products

• VMware Data Services Manager for VCF

Issue/Introduction

Symptoms

When attempting to upgrade VMware Data Services Manager (DSM) from version 2.2.1.6070 to 2.2.3.1196, the process fails during the PROVIDER UPDATE stage.

The following error status is observed in the DSM Management console: PROVIDER PROVIDER UPDATE Install provider-update Source Version - [2.2.1.6070] to Target Version - [2.2.3.1196] FAILED

 

Environment

VMware Data Services Manager 2.2.1

Cause

This issue is caused by a known race condition in DSM 2.2.1 where the vpostgresql service on the DSM manager starts before all necessary system dependencies are fully initialized during the reboot sequence. This results in the statistics collector and autovacuum features failing to start, which prevents the upgrade provider from completing its tasks.

To confirm this issue, check the PostgreSQL logs on the DSM appliance:

1. Log in to the DSM appliance shell via SSH as root.
2. Examine the log file at /data/vpgsql/vpgsql.log.
3. Look for the following error traces:

• LOG: could not send test message on socket for statistics collector: Operation not permitted
• LOG: disabling statistics collector for lack of working socket
• WARNING: autovacuum not started because of misconfiguration

Resolution

This is a known issue in DSM version 2.2.1. A permanent fix is included in version 2.2.2 and later. To proceed with the upgrade to 2.2.3, use the following workaround to restart the affected service:

1. Log in to the DSM appliance shell as root.

2. Restart the PostgreSQL service to ensure all system dependencies are available:

3. bash  'systemctl restart vpostgresql.service'

4. Verify the service has started cleanly by checking the log file again (/data/vpgsql/vpgsql.log) to ensure the "disabling statistics collector" warning is no longer appearing.

5. Return to the DSM Management UI and re-initiate the Control Plane upgrade.