[VMC on AWS] Inability to Edit VM Settings in an SDDC which is linked to another SDDC via SDDC Group

Products

• VMware Cloud on AWS

Issue/Introduction

To understand why this issue occurs and the next plan of action.

Symptoms:

Issues encountered while attempting to edit settings for virtual machines (VMs) in SDDC2.

An error message stating, "An error occurred while trying to load data. This could be due to temporary outage. You can retry the operation by clicking the retry button"

was displayed during the process where the SDDC is linked to another SDDC and one of the SDDCs would be on the 1.18vx version.

 

Cause

This is a known issue in SDDC Version 1.18.
This is fixed in SDDC Version 1.20.

Resolution

Request an SDDC upgrade to SDDC version 1.20+.

Alternatively, customers can reach out to CSMs to get the SDDC upgrades scheduled on their behalf.

Workaround:

The following 5 steps will work around the issue:

 

1.) Verification of vCenter Linking

Initially, confirm that both the vCenter instances associated with SDDC1 and SDDC2 are properly linked. Despite the linking, attempting to modify VM settings in SDDC2 would lead to the aforementioned error message, while no such issue would be observed in SDDC1.

 

2.) Temporary vCenter Unlinking

To isolate the issue, temporarily unlink both vCenter instances from the VMware Cloud (VMC) console.

 

3.) Validation of Independent vCenter Operation

After unlinking both vCenter instances, confirm that each vCenter is able to function independently. The ability to edit VM settings within SDDC2 is to be tested in this state, and confirm that the issue no longer occurred.

 

4.) Re-establishing vCenter Link

Once the successful editing of VM settings within SDDC2 is confirmed with independent vCenter operation, the next step involves re-linking the vCenter instances through the VMC console.

 

5.) Successful Relinking and Editing

Following the re-establishment of vCenter linkage, both vCenter instances must be visible in a unified interface. Notably, it should be verified that the issue causing the error message is resolved. Users should now be able to edit the settings of VMs in both SDDC1 and SDDC2 without encountering any errors.

 

Additional Information

Impact/Risks:

Customer will be unable to edit VM settings.