Users unable to view their existing deployments after upgrading from Aria Automation 8.18 to VCF Automation 9.0.x

Products

• VCF Automation

Issue/Introduction

• After upgrading from Aria Automation 8.18.x to VMware Cloud Foundation (VCF) Automation 9.0.2, certain users are unable to see their pre-existing deployments in Service Broker.

• Administrators can still see all deployments without issue.

• Users experiencing this issue can successfully see new deployments created after the upgrade.

• The affected users typically had mixed-case usernames or full names in the previous 8.18 environment (e.g., Firstname.Lastname or Mixed.Case).

Environment

VCF Automation 9.0.x

Cause

This issue is caused by a case-sensitivity mismatch following the identity management migration during the upgrade.

During the upgrade to VCF Automation 9.x, user formats are converted and perceived in lowercase (e.g., Firstname.Lastname becomes firstname.lastname). However, the existing deployments table still stores the legacy mixed-case name in the ownedBy attribute.

Resolution

This is a known issue. A code fix to will be included in the upcoming release.

Additional Information

Workaround

To restore visibility of the deployments for the affected users, you must update the ownedBy attribute to the new lowercase format.

Steps:

1. Log in to VCF Automation as an Administrator.

2. Locate the missing deployment.

3. Change the ownership of the deployment to a completely different user or a group within the project.

   • Note: You cannot directly change the owner from Firstname.Lastname to firstname.lastname because VCF Automation recognizes them as the same underlying user identity.

4. Change the ownership of the deployment back to the original user.

By passing the ownership to an intermediary and back, the deployment's ownedBy attribute is forcefully updated to the new lowercase username format (firstname.lastname), restoring the user's visibility.