Upgrade to 30.2.5 failed due to datapath health monitor not present for a Site Persistence enabled GSLBService

Products

• VMware Avi Load Balancer

Issue/Introduction

When upgrading from a previous version to 30.2.5 or above, the upgrade may fail with the following message:

"Migration failed for object of type GslbService, with uuid gslbservice-xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx at function upgrade_GslbService for version 30.2.5 with exception: (\"GslbService 'testgslbservice' 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.\",)  

Environment

Avi deployments in versions below 30.2.5 having GSLBServices with Site Persistence enabled but do not have datapath health monitor configured for them.

Cause

Previously, Datapath Health Monitors were optional for SP enabled GslbService(s). To address DNS resolution inconsistencies during reboots or site-to-site connectivity failures, we now mandate from 30.2.5 version that all SP-enabled GslbService(s) include a Datapath Health Monitor.

Resolution

For the GSLBService mentioned in the upgrade failure message, prior to the upgrade, attach a datapath health monitor to it as shown in screenshot below.