When attempting to expand a vSAN stretched cluster in a VMware Cloud Foundation (VCF) 9.0.2 environment, the SDDC Manager expansion workflow fails. The following symptoms are observed:
InternalServerError./var/log/vmware/vcf/domainmanager/domainmanager.log file contains java.lang.NullPointerException similar to the following: ERROR [vcf_dm...] Failed to update cluster java.lang.NullPointerException: Cannot invoke "java.util.List.iterator()" because "nameContextList" is nullDEBUG [vcf_dm...] Cluster name context list null for cluster [Cluster_Name].VCF 9.x
This stems from a known issue in VMware Cloud Foundation 9.0.0 inventory synchronization process. During sync operations, the name_context metadata is incorrectly stripped from the cluster data model in the SDDC Manager platform database. If a synchronization occurred while the environment was on version 9.0.0, the field remains blank even after upgrading to version 9.0.1 or 9.0.2.
The stretched cluster workflow relies on this name_context metadata to identify and iterate through the availability zone. Because the value is null, the Stretch workflow cannot initialize the necessary iterator, resulting in failure.
The issue where inventory synchronization strips metadata from the name_context field is resolved in VCF 9.0.1.0.
To remediate this in existing environments, you must manually restore the missing metadata within the SDDC Manager platform database.
root user and connect to the database: psql -h localhost -U postgres -d platformname_context is null (replace [cluster_id] with your actual cluster ID: SELECT id, name, name_context FROM cluster WHERE id = '[cluster_id]';[ClusterName] with the display name of your cluster and [cluster_id] with the ID): UPDATE cluster SET name_context = '[{"context":"STRETCH","name":"[ClusterName]"}]' WHERE id = '[cluster_id]';Note: It is recommended to take an offline snapshot of the SDDC Manager VM before performing manual database modifications.