VIC 1.4 Admiral fails to load despite successful registration
lgayatri opened this issue · 3 comments
lgayatri commented
@lgayatri commented on Tue Mar 20 2018
For bug reports, please include the information below:
Please fill out both the Basic Information and Detailed Information sections.
Bug Report Basic Information
REQUIRED:
- vCenter Server version: 6.7 , 7989256
- Embedded or external PSC: Embedded
- Filename of the OVA you deployed: https://storage.googleapis.com/vic-product-ova-builds/vic-dev-v1.4.0-dev-4105-e1b1972c.ova
- Does the VIC appliance recieve configuration by DHCP? No static
- What stage of the Appliance Lifecycle is the VIC appliance in? Registration succeeded but admiral failed to load
https://github.com/vmware/vic-product/blob/master/installer/docs/SUPPORT.md#appliance-lifecycle - Attach the VIC appliance support bundle (e.g. vic_appliance_logs_2018-01-01-00-01-00.tar.gz)
https://github.com/vmware/vic-product/blob/master/installer/docs/SUPPORT.md
vic_appliance_logs_2018-03-20-10-20-17.tar.gz
Bug Report Detailed Information
- What operation was being performed when the failure was noticed?
Was registering VIC with VCSA
@lazarin commented on Tue Mar 20 2018
Are all clocks in sync? (probably between appliance and PSC)?
I see following when registergin solution user in the logs:
The time now Tue Mar 20 09:28:37 UTC 2018 does not fall in the request lifetime interval extended with clock tolerance of 600000 ms: [ Tue Mar 20 09:41:20 UTC 2018; Tue Mar 20 10:11:20 UTC 2018). This might be due to a clock skew problem. Please see the server log to find more detail regarding exact cause of the failure
there's some time tolerance of 10min but the diff is ~42min
@lgayatri commented on Tue Mar 20 2018
VIC appliance somehow jumped clock. Setting it back and checking
lgayatri commented
lgayatri commented
afilipov1 commented
Fix is submitted and a new jar is produced and sent to the ova team.