Add time info

installer/build/scripts/systemd/scripts/support/appliance-support.sh

@@ -121,6 +121,7 @@ function getPrivateFiles {
 function getDiagInfo {
   # Appliance
   commandToFile "hostnamectl" "hostnamectl" "appliance"
+  commandToFile "timedatectl" "timedatectl" "appliance"
   commandToFile "ip address show" "ip_addr" "appliance"
   commandToFile "ovfenv" "ovfenv" "appliance"
   commandToFile "cat /etc/vmware/environment" "environment" "appliance"

installer/docs/SUPPORT.md

@@ -10,16 +10,17 @@ This information about the environment and events that occurred leading to the f
 - Embedded or external PSC?
 - Filename of the OVA you deployed
 - Hash (MD5, SHA-1, or SHA-256) of the OVA you deployed
+- Does the VIC appliance recieve configuration by DHCP?
 - IP address of VIC appliance
 - Hostname of VIC appliance
 - IP address of vCenter Server
 - Hostname of vCenter Server
 - What stage of the [Appliance Lifecycle](#appliance-lifecycle) is the VIC appliance in?
 - What operation was being performed when the failure was noticed?
 
-_IMPORTANT_
+*IMPORTANT*
 
-If you are using VIC appliance version 1.3.1 or greater and are able to SSH into the appliance, please run `/etc/vmware/support/appliance-support.sh` and provide the resulting file to support. This script gathers appliance state and log information and is the best tool for gathering comprehensive support information.
+If you are using VIC appliance version 1.3.1 or greater and are able to SSH into the appliance, please run `/etc/vmware/support/appliance-support.sh` and provide the resulting file to support. This script gathers appliance state and log information and is the best tool for gathering comprehensive support information. Provide this output for all support requests along with additional Support Information from the corresponding stage of the Appliance Lifecycle.
 
 
 ## Appliance Lifecycle
@@ -56,7 +57,7 @@ Provide the following information to support if encountering Deployment failures
 
 ### Boot Stage
 
-After the VIC appliance is deployed, it is powered on and boots. During this time the appliance applies user provided configuration, starts an SSH server, and starts certain services. Soon after the network interface comes up, SSH will become available on the appliance and a server on port 80 will display a message that appliance services are starting. In version 1.3.0, there may be a significant delay before the web page is available on port 80. 
+After the VIC appliance is deployed, it is powered on and boots. During this time the appliance applies user provided configuration, starts an SSH server, and starts certain services. Soon after the network interface comes up, SSH will become available on the appliance and a server on port 80 will display a message that appliance services are starting. In version 1.3.0, there may be a significant delay before the web page is available on port 80. In version 1.3.1, a message will be displayed while appliance services are starting, but you must refresh the page periodically until the Getting Started Page is displayed when the appliance is ready.
 
 #### Boot Failures
 
@@ -174,6 +175,17 @@ Provide the following information to support if encountering Initialization fail
       resulting output to support
     - If the version is 1.3.1 or less, run `journalctl -u harbor_startup` and provide the entire
       resulting output to support
+- If Admiral is not running and `systemctl status get_token` shows that the service failed, check
+  `journalctl -u get_token`
+    - If the logs show errors obtaining tokens and mentioning clock skew, there may be clock skew
+      between the appliance and the PSC
+        - The appliance recieves NTP configuration from DHCP by default. If DHCP is not used, set
+          time synchronization by one of these two methods:
+            - Set "Synchronize guest time with host" in vSphere, shutdown guest OS, and power on to
+              apply the setting (not restart/reboot)
+              [https://kb.vmware.com/s/article/1014038](https://kb.vmware.com/s/article/1014038)
+            - SSH into the appliance and configure NTP by `timedatectl set-ntp true`. NTP servers
+              can be customized in `/etc/systemd/timesyncd.conf`.
 - If the Admiral web interface shows an error `SsoManager has not been initialized at runtime`, see [Admiral Troubleshooting Guide](https://github.com/vmware/admiral/wiki/Troubleshooting-VIC).
 - If Admiral is not running, did you provide custom TLS certificates during the Deployment Stage?
     - If yes, verify the format is correct [Certificate Reference](#additional-information)