Issue with starting timesyncd service after upgrading to VMware Cloud Director 10.6.0

Products

• VMware Cloud Director

Issue/Introduction

• After an upgrade from VMware Cloud Director 10.5.1.1 to VMware Cloud Director 10.6.0 you can see the timesyncd service are not running in the VMware Cloud Director cells.
• Even after rebooting the VMware Cloud Director cells the timesyncd service does not start.
• The NTP settings configured on the Cells look correct.
• The NTP service is not running by default.

Environment

VMware Cloud Director 10.6
VMware Cloud Director 10.6.0.1

Cause

This is a known issue affecting the mentioned versions of VMware Cloud Director. 

Resolution

As a workaround, the issue can be resolved by manually enabling and starting the timesyncd service in each cell using the below command:

1. Re-enable the service to ensure it will start again on next boot:
   systemctl enable systemd-timesyncd
   
   
2. Start the service after enabling it:
   systemctl start systemd-timesyncd
   
   
3. Confirm it is now running:
   systemctl status systemd-timesyncd