DSM connector stuck in Pending state or fails with 403 Forbidden in VMware Cloud Foundation Automation

Products

• VCF Automation

Issue/Introduction

The Data Services Manager (DSM) connector in VMware Cloud Foundation Automation remains in a "Pending" state, preventing the connection from being established. Attempts to remove or re-add the connector fail, and attempts to uninstall the DSM service via the portal or API return a "403 Forbidden" error.

Environment

• VMware Cloud Foundation Automation (VCFA) 9.1
• Data Services Manager (DSM) 9.1

Cause

This issue occurs because the user account performing the DSM service operations (install, uninstall, or manage) is assigned a custom role, such as a cloned "admin" role. The DSM service requires privileges that are only available to the built-in "System Administrator" role.

Resolution

To resolve this issue, you must perform service operations using an account with the built-in "System Administrator" role.

1. Log in to VMware Cloud Foundation Automation with a user account that has the full "System Administrator" role.
2. If you are currently using a custom or cloned administrator role, update the user account permissions to revert to the default built-in "System Administrator" role.
3. Once the role is updated, retry the uninstallation or management operation in the DSM service.
4. If the connection remains stuck in a "Pending" or "Deleting" state after applying the correct role, wait for the task to reconcile or attempt the operation again using the updated account permissions.

Additional Information

If you require further assistance after verifying the role permissions, contact Broadcom Support. Subscribe to a Broadcom knowledge article by article or product to get updates on this issue.