Bug 1404417 – Build status will report "running for -1h"

Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.

Bug 1404417 - Build status will report "running for -1h"

Summary:	Build status will report "running for -1h"

Status:	CLOSED ERRATA

Aliases:	None

Product:	OpenShift Container Platform
Classification:	Red Hat
Component:	Management Console (Show other bugs)
Sub Component:
Version:	3.3.1
Hardware:	Unspecified Unspecified

Priority	medium Severity medium
Target Milestone:	---
Target Release:	---
Assigned To:	Jessica Forrester
QA Contact:	Yadan Pei
Docs Contact:

URL:
Whiteboard:
Keywords:

Duplicates:	1432158 (view as bug list)
Depends On:
Blocks:
	Show dependency tree / graph

Reported:	2016-12-13 14:31 EST by Will Gordon
Modified:	2017-07-24 10 EDT (History)
CC List:	5 users (show)

See Also:
Fixed In Version:
Doc Type:	Bug Fix
Doc Text:	Cause: Relative time and duration calculations were not preventing negative numbers from showing. Consequence: Under normal client and server clock situations negative numbers would not happen. However when there was clock skew between the browser client and the server then negative times could appear on objects like builds in the console. Fix: Prevent relative times and durations from returning negative values by forcing them to zero. Result: Negative relative times and durations will not appear in the console.
Story Points:	---
Clone Of:
Environment:
Last Closed:	2017-04-12 15:18:28 EDT
Type:	Bug
Regression:	---
Mount Type:	---
Documentation:	---
CRM:
Verified Versions:
Category:	---
oVirt Team:	---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---

Attachments	(Terms of Use)
Image of problem in action (30.40 KB, image/png) 2016-12-13 14:32 EST, Will Gordon	no flags	Details
Add an attachment (proposed patch, testcase, etc.)

External Trackers
Tracker	ID	Priority	Status	Summary	Last Updated
Red Hat Product Errata	RHBA-2017:0884	normal	SHIPPED_LIVE	Red Hat OpenShift Container Platform 3.5 RPM Release Advisory	2017-04-12 18:50:07 EDT

Groups: None (edit)

Description Will Gordon 2016-12-13 14:31:13 EST

Description of problem:
When running `oc start-build <name> --from-repo=../<name>" the web console updates with "waiting for -1h" or "running for -1h".


Version-Release number of selected component (if applicable):
v3.3.1.3

How reproducible:
Every time, however, it's only brief until it starts to count up normally in seconds

Steps to Reproduce:
1. oc start-build <name> --from-repo=../<name>
2.
3.

Actual results:
Running for -1h

Expected results:
Running for 1s

Additional info:

Comment 1 Will Gordon 2016-12-13 14:32 EST

Created attachment 1231317 [details]
Image of problem in action

Comment 2 Jessica Forrester 2016-12-13 15:01:04 EST

Negative durations should no longer appear, this has already been fixed for origin 1.5

Comment 3 Jessica Forrester 2016-12-13 15:03:52 EST

actually we fixed one of the duration filters but not the other. will fix the other one

Comment 4 openshift-github-bot 2016-12-13 16:02:35 EST

Commit pushed to master at https://github.com/openshift/origin-web-console

https://github.com/openshift/origin-web-console/commit/9b35ca7feb2804913f006b79098d43cd050302bc
Bug 1404417 - Don't show negative durations, they are always due to client clock skew

Comment 5 Troy Dawson 2017-01-20 17:57:39 EST

This has been merged into ocp and is in OCP v3.5.0.7 or newer.

Comment 6 Yadan Pei 2017-01-23 22:11:14 EST

Checked against v3.5.0.7+390ef18

When Build is in New & Pending status, Duration will not be calculated, neither will be shown in table(See attachment NewPending)

Duration will be calculated from 0 seconds when builds changes to Running(See attachment PendingtoRunning)


Move to VERIFIED

Comment 9 Jessica Forrester 2017-03-14 13:36:32 EDT

*** Bug 1432158 has been marked as a duplicate of this bug. ***

Comment 11 errata-xmlrpc 2017-04-12 15:18:28 EDT

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2017:0884

Note You need to log in before you can comment on or make changes to this bug.