“Failed to fetch users. Role with id LCM Admin could not be found" error message in User Management tab on Aria Suite Lifecycle

Products

• VCF Operations/Automation (formerly VMware Aria Suite)

Issue/Introduction

When navigating to the User Management tab in VMware Aria Suite Lifecycle, the UI displays the following error:

"Failed to fetch users. Role with id LCM Admin could not be found" 

 

Environment

Aria Suite Lifecycle 8.x

Cause

Logs show that for user admin@local, although the user has a valid role assignment, the system attempts to resolve a role using a role name instead of its GUID:

UserRoleMappingDTO [uservmid=dddd-dddd-dddd-dddd, rolevmid=LCM Admin]

The rolevmid field incorrectly contains the literal value "LCM Admin" rather than the expected GUID (e.g., aaaa-aaaa-aaaa-aaaa).

Correct behavior:

Role GUIDs (e.g., aaaa-aaaa-aaaa-aaaa) must be stored in rolevmid.

The logs confirm that other users correctly map to GUIDs, while the problematic user does not.

Evidence from logs:

For a working user:

UserRoleMappingDTO [uservmid=bbbb-bbbb-bbbb-bbbb, rolevmid=aaaa-aaaa-aaaa-aaaa]

For the failing user:

UserRoleMappingDTO [uservmid=dddd-dddd-dddd-dddd, rolevmid=LCM Admin]

Database query also confirms that the admin@local user (vmid=cccc-cccc-cccc-cccc) is assigned correctly, but the log shows a mismatch, indicating inconsistent or corrupted entries.

Resolution

Correct the roleVMID values in the vm_user_role_mapping table so they reference the proper role GUIDs, not role names.

Steps:

1. Identify the correct role GUID for the LCM Admin role (typically GUID: aaaa-aaaa-aaaa-aaaa).
2. Validate the following tables for consistency:
   1. vm_user_role_mapping
   2. vm_user
   3. vm_group
   4. vm_group_role_mapping

3. Update any rows in vm_user_role_mapping where roleVMID contains an invalid string (such as "LCM Admin") and replace it with the correct GUID (e.g., aaaa-aaaa-aaaa-aaaa)

4. Ensure the userVMID for admin@local (GUID: cccc-cccc-cccc-cccc) is correctly mapped to the LCM_ADMIN role GUID.

5. Re-test the User Management tab.