Cell connectivity is lost after upgrading VMware Cloud Director.

Products

• VMware Cloud Director

Issue/Introduction

Symptoms:

• After upgrading Cloud Director, the Cells can no longer reach expected endpoints.
• Static routes on a Cell are no longer present after upgrading.
• Running "ovfenv" from the command line of a Cell yields no results after upgrade.

Environment

VMware Cloud Director 10.x
VMware Cloud Director for Service Provider 10.x

Cause

This issue occurs when the OVF Environment variables cannot be refreshed.

• This could occur for a number of reasons (i.e.: vCenter is down, cell unable to connect with vCenter, etc.)

Resolution

• This is a known issue impacting Appliance upgrades to 10.4.x versions of VMware Cloud Director.

Workaround:

1. Backup the file /etc/systemd/system/vcd-ova-netconfig.service.
2. Edit the file /etc/systemd/system/vcd-ova-netconfig.service and replace the first three lines with:
       [Unit]
       Description=Cloud Director Appliance Network Configuration Service
       Before=vpostgres.service vmware-vcd.service
       After=network.target systemd-networkd.service vaos.service
3. Reboot the appliance.

This should improve the reliability of picking up OVF properties that are set in vCenter's vApp Options interface.

4. If you encounter issues after running Step 3, revert to the backup captured in Step 1.
   1. Engage Technical Support.
5. Otherwise, please continue with Steps 1-4 on all remaining Cells in the Server Group.

Additional Information

Impact/Risks:

• Cloud Director may have issues connecting to endpoints beyond it's directly connected subnets.
• The impact will vary depending on environmental specifics such as the subnet location of external elements such as the Transfer Share, NSX Manager(s) and vCenter Server(s).