Hi Falks,
Today I had to try upgrade our vRealize Operation 6.4 environment (One Operation Manager node and one Remote Collector node) but after when I uploaded OS upgrade pak file, I got error message.
In the logs i see this:
2017-05-24 08:44:31,450 - b2b - DEBUG - validate - casa_call - Response from url /casa/sysadmin/slice/ntp/current_time to host 192.168.xxx.xx4
2017-05-24 08:44:31,450 - b2b - DEBUG - validate - casa_call - {
"currentTime": 1495608164731
}
2017-05-24 08:44:31,450 - b2b - DEBUG - validate - time_sync_check - slice 192.168.xxx.xx4 --- timestamp 1495608164704
2017-05-24 08:44:31,466 - b2b - DEBUG - validate - casa_call - Response from url /casa/sysadmin/slice/ntp/current_time to host 192.168.xxx.xx5
2017-05-24 08:44:31,466 - b2b - DEBUG - validate - casa_call - {
"currentTime": 1495608271463
}
2017-05-24 08:44:31,466 - b2b - DEBUG - validate - time_sync_check - slice 192.168.xxx.xx5 --- timestamp 1495608271420
2017-05-24 08:44:31,466 - b2b - ERROR - validate - main - The node(s) "192.168.xxx.xx4", "192.168.xxx.xx5" are not in time sync and vary by "106"seconds
2017-05-24 08:44:31,466 - b2b - DEBUG - validate - update_state_file - Updating state file with check: time_sync_check, start_time: False, stop_time: True, result: False, result_desc: The node(s) "192.168.xxx.xx4", "192.168.xxx.xx5" are not in time sync and vary by "106"seconds
We use NTP server (this is recommended) which is an AD server to. Operation Manager says status is ok.
When we upgraded from 6.2 to 6.3 and 6.3 to 6.4 we hadn't problem during upgrade.
I found a KB Article (How to change the date, time, or time zone of a vApp-based vRealize Operations Manager node (2108686) | VMware KB ) but I would like to use NTP so far now.
Anybody have idea or same problem?
Thx!
Tibor