Upgrade Aborts During Config Migration with Error: "GslbService Has Site Persistence Enabled but Does Not Have a Datapath Health Monitor"

Products

• VMware Avi Load Balancer

Issue/Introduction

 

• During an upgrade of VMware Avi Load Balancer, the upgrade process may abort during the Config Migration phase. This occurs when one or more GSLB Services have Site Persistence enabled but do not have a Datapath Health Monitor attached a configuration that is now enforced as a requirement in newer releases.

 

• The upgrade will fail with the 'UPGRADE_FSM_ABORTED' error due to an issue with the running task MigrateConfig. This can be identified by running the command:

• controller:>show upgrade status detail

                                                                     |
|         sub_tasks[1]   | Migration failed for object of type GslbService, with uuid gslbservice-####### |
|                        | ### at function upgrade_GslbService for version 30.2.5 w |
|                        | ith exception: ("GslbService '##############' has Site Per |
|                        | sistence enabled but does not have a datapath Health Monitor. To proceed with th |
|                        | e upgrade, please attach a datapath Health Monitor to all GslbServices that have |
|                        |  Site Persistence enabled.",)  Migration failed  with exception: ('Errors counte |
|                        | red for [\'GslbService\'].\nUC::Migration failed for object of type GslbService, |
|                        |  with uuid gslbservice-########### at function upgrade_ |
|                        | GslbService for version 30.2.5 with exception: ("GslbService |
|                        |  has Site Persistence enabled but does not have a datapath  |
|                        | Health Monitor. To proceed with the upgrade, please attach a datapath Health Mon |
|                        | itor to all GslbServices that have Site Persistence enabled.",)                  
|

 

• SSH to the Controller Leader node using the admin credentials and check the upgrade coordinator log located on the previous partition: /host/prev/var/lib/avi/log/upgrade-coordinator.log

• From this log, you can observe that the upgrade failure was caused during the migration of the GSLB service.

[2026 INFO [upgrade_tasks.get_other_process_upgrade_events:1207] High level migration logs: Migration failed for object of type GslbService, with uuid gslbservice-########### at function upgrade_GslbService for version 30.2.5 with exception: ("GslbService '#########' has Site Persistence enabled but does not have a datapath Health Monitor. To proceed with the upgrade, please attach a datapath Health Monitor to all GslbServices that have Site Persistence enabled.",)
 Migration failed  with exception: ('Errors countered for [\'GslbService\'].\nUC::Migration failed for object of type GslbService, with uuid gslbservice-######### at function upgrade_GslbService for version 30.2.5 with exception: ("GslbService \############\' has Site Persistence enabled but does not have a datapath Health Monitor. To proceed with the upgrade, please attach a datapath Health Monitor to all GslbServices that have Site Persistence enabled.",) ::UC\nFor further details please refer to the upgrade journals.',)

 

Environment

• Avi Load Balancer
• Affected Version: 31.2.x, 31.1.2, 30.2.5 and above

Cause

 A GSLB Service with Site Persistence enabled must have a Datapath Health Monitor configured. Avi now enforces Datapath health monitoring for such GSLB configurations.

This requirement was introduced as an enhancement in newer releases to prevent service disruption scenarios, such as:

• Inter-site Service Engine (SE-to-SE) connectivity loss

• Upgrades or reboots at peer sites

Resolution

Workaround:

Follow the steps below to resolve the issue:

1. Navigate to Applications > GSLB Services in the VMware Avi Load Balancer UI.

2. Identify all GSLB Services that have Site Persistence enabled.

3. For each of these services, attach a Datapath Health Monitor if it's not configured.

4. Ensure the configuration changes are saved successfully.

5. Once completed, retry the upgrade.