This issue has been observed in a scenario where a specific TKGI cluster was not fully upgraded before performing a new upgrade on it.
Workaround:
1) Review the manifest for this specific TKGI cluster
You may download the manifest for TKGI cluster using the service-instance_ID and check if the field nsxt_node_ip_block_ids exists
tkgi clusters
bosh -d service-instance_ID manifest > service-instance_ID.ymlgrep nsxt_node_ip_block_ids service-instance_ID.yml2) If the field
nsxt_node_ip_block_ids is missing, you may manually add into the manifest file
cp service-instance_ID.yml service-instance_ID_backup.ymlvim service-instance_ID.yml- Just after the line
nsxt_network: true in the manifest, add
nsxt_node_ip_block_ids and the
name (retrieve it from TKGI tile > settings > Networking >
Nodes IP Block ID)
nsxt_network: true
nsxt_node_ip_block_ids:
- name: 1ab1ab11a-1234-410c-be80-786cfd6be1af
3) Deploy the manifest:
bosh -d service-instance_ID deploy service-instance_ID.yml4) Upgrade the TKGI cluster
tkgi upgrade-cluster CLUSTERNAME