Virtual Service placement is stuck at `OPER_RESOURCES` with error "No network/subnet matched Virtual Service IP..."

Products

• VMware Avi Load Balancer

Issue/Introduction

After an SE reboot, the virtualservice placement may get stuck at `OPER_RESOURCES` with the error "No network/subnet matched Virtual Service IP x.xx.xx.xx. Configure Virtual Service placement settings with the required network/subnet." as seen in the screenshot below

Environment

Avi Load Balancer. - 22.1.2 and prior

Cause

The VS is having problem getting placed because the Discovered Networks field in the Vip Configuration has been removed due to an internal race condition.

Currently, placement subsystem only acts on discovered networks for Vip placement. If that field is missing, placement will not be able to resolve the network for Vip. The field can be filled/resolved again by Updating the config, like disable/enable of the VsVip.

This can be confirmed by checking the discovered_network field in vip configuration via CLI using the show command - show vsvip <vsvip>. 

Resolution

This issue is fixed in version 22.1.2-2p3, 22.1.3 and above.

 

Workaround:

• Disable/Enable vip (Not VirtualService) to recompute the discovered networks in the vip configuration.
• This can be done via CLI for VSes created by TKG/AKO :
  
  To disable VsVip
  
  > configure vsvip <vsvip>
> vip index 1
> no enabled
> save
> save
  
  To enable VsVip
  
  > configure vsvip <vsvip>
> vip index 1
> enabled
> save
> save