Upgrading VMware Data Services Manager from version 2.2.0 to 2.2.1 may fail with "Error generating upgrade marker file" seen in providerupdatemanager.log.

Products

• VMware Data Services Manager

Issue/Introduction

This article describes the method to overcome potential upgrade failure from VMware Data Services Manager 2.2.0 to 2.2.1. 
This is applicable only when upgrade from 2.2.0 to 2.2.1 fails with the error mentioned in resolution section.


Environment

VMware Data Services Manager

Cause

During a control plane upgrade, if the VMware Data Services Manager's provider backup repository is configured, the upgrade sometimes fails to mark the last successful backup point before the upgrade.


Resolution

Symptoms :

   1. The Provider Update task is marked as failed in the UI, and the VMware Data Services Manager appliance remains on previous version 2.2.0, still accessible for all operations (i.e., the appliance is up and running).

   2. Issue can be confirmed by checking whether /var/log/tdm/provider/providerupdatemanager.log contains the error trace similar to:

   com.vmware.tdm.sp.common.exception.TdmException: Error generating upgrade marker file. begin -1, end 0, length 0
   at com.vmware.tdm.sp.provider.update.manager.fsm.service.ProviderUpdateApplyService.generateUpgradeMarker(ProviderUpdateApplyService.java:190)

 

If the above trace is found in the log file, user should unblock the upgrade by following the steps below:
   
   1. Log into the appliance (as root) using ssh and Edit the postgresql.conf file using:

"vi /data/vpgsql/postgresql.conf"

   2. Uncomment the wal_keep_size property and set its value to 200MB as follows: wal_keep_size = 200MB.

   3. Save the file

   4. Reload the vPostgreSQL server using the following command:

"su - postgres -c "pg_ctl reload -D /data/vpgsql"

   5. Reinitiate the control plane upgrade from the VMware Data Services Manager UI portal.