Unable to save setting in Service Engine Group

Products

• VMware Avi Load Balancer

Issue/Introduction

When attempting to edit or update a Service Engine Group (SEG) in VMware Avi Load Balancer, the following error is observed:

ServerFaultCode: Request missing value for required parameter 'profileIds' to method 'PbmRetrieveContent'

The operation fails and the SEG configuration cannot be saved.

Environment

 

• VMware Avi Load Balancer version 31.2.1 or later
• Deployment mode: Write Access Mode with vCenter/NSX-T Cloud

 

Cause

Starting with Avi Load Balancer version 31.2.1, a new VM Storage Policy feature was introduced. This feature requires the vCenter service account used by Avi (assigned the Avi Global Role) to have explicit permissions to interact with vSphere Storage Policy Based Management (SPBM) — specifically the PbmRetrieveContent API method.

If the following Storage Policy privileges are missing from the Avi Global Role assigned to the vCenter service account, the SEG edit operation invokes the SPBM API without the required authorization, resulting in the ServerFaultCode error:

• Apply VM storage policies
• View VM storage policies

Resolution

Add the required Storage Policy privileges to the vCenter roles assigned to the Avi service account by following these steps:

1. Log in to the vSphere Client with an administrator account.
2. Navigate to Administration → Roles.
3. Edit the Avi Global Role assigned to the Avi service account.
4. Under Privileges, locate the Storage Policy category and enable:
   
   Apply VM storage policies
   View VM storage policies
   
   
5. Additionally, review and correct privilege levels for both the Avi Global Role and the Avi SE Folder Role as per the official Broadcom documentation and re-assign both roles to the Avi service account.
6. Save the role changes and retry editing the Service Engine Group.

Additional Information

This issue is specific to environments that upgraded to or freshly installed Avi Load Balancer 31.2.1+ without updating the vCenter role permissions accordingly. Environments on versions prior to 31.2.1 are not affected