Description
During longevity test I started to notice this behavior and checked several different browsers, machines, and people, verifying same behavior.
Not sure if environment as cluster does not have any ntp clock synchronization.
Also only seeing this on orchestrator: 172.23.106.14:8091. If I use a different node in cluster the cluster then it's ok.
Attached recordings from local mac and rdesktop of windows machine in lab. +cbcollect
Attachments
Issue Links
- blocks
-
MB-20290 4.6.0 Point Release
- Closed