Virtual Service remains active after Datascript removal and without pool configuration

Products

• VMware Avi Load Balancer

Issue/Introduction

• When a datascript is detached or removed from a Virtual Service that lacks a configured pool, the Virtual Service fails to go down as expected. Consequently, traffic continues to be directed to the VS, leading to application traffic disruption
• This behavior disrupts application traffic, as the VS should ideally go down under these circumstances as there is no backend pool present to serve the traffic.

Cause

• The root cause of this issue is that the removal of the datascript does not properly remove the internal link to the previously associated pool or pool group. This lingering link prevents the Virtual Service from transitioning to a down state.

Resolution

Workaround:

• Disable & re-enable Virtual Service. This action forces the VS to correctly recognize the absence of a pool and properly transition to a down state

Additional Information

Please note that virtual service will be available, up and accept client traffic if one of the following conditions is met:

• At least one of the pools associated to the virtual service is up.
• A policy (for example, a redirect policy) associated with the virtual service that does not need a pool
• A DataScript attached to the policy.
• The virtual service is associated to a policy that sends a local response.

https://techdocs.broadcom.com/us/en/vmware-security-load-balancing/avi-load-balancer/avi-load-balancer/30-2/vmware-avi-load-balancer-configuration-guide/load-balancing-overview/virtual-services.html