Description of problem: OpenShift console displays incorrect (possibly positive or negative) counter time when a build is started. Version-Release number of selected component (if applicable): How reproducible: Seems to happen every time I start a build with the web console. Steps to Reproduce: 1. Log into OSE web console (using Google Chrome on Windows 7). 2. Select an existing project. 3. Browse -> Builds 4. Select a pre-existing build. 5. Click "Start Build" Build is listed in the table but "Status" "Running for..." time seems to be calculated based on the local time where my browser is running (time on my laptop) whereas the "Created" timestamp comes from the server running OSE. The times listed for the build in the CLI using oc describe use the server time and work fine but the counter in the console will be incorrect (until the build finishes) if the server time and browser environment time are different. It will start out negative if the local time is behind the server time and start out positive if the local time is ahead of the server time. Actual results: Running for time is incorrect by the difference between the OSE server clock and the web console user's local clock. Expected results: "Running for" time in the console matches what "oc describe" outputs. Both should use the server's time to calculate "Running for" time. Additional info:
@cewong what is the CLI doing to calculate how long the build has been running
This shouldn't be an issue of timezones, this would be an issue of clock skew. Either the client's clock or the server's clock was not on the correct time.
*** This bug has been marked as a duplicate of bug 1371764 ***
Just reminder: Though marked duplicate, this bug's Version field is 3.2.0 while bug 1371764 is reported against 3.3. So there is a concern: given bug 1371764 is fixed, whether need backport the fix to 3.2.