Bug 1565479 – no time for updated-at field

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

Bug 1565479 - no time for updated-at field

Summary:	no time for updated-at field

Status:	CLOSED ERRATA

Aliases:	None

Product:	Red Hat Gluster Storage
Classification:	Red Hat
Component:	web-admin-tendrl-api (Show other bugs)
Sub Component:
Version:	3.4
Hardware:	Unspecified Unspecified

Priority	unspecified Severity unspecified
Target Milestone:	---
Target Release:	RHGS 3.4.0
Assigned To:	Shirshendu Mukherjee
QA Contact:	Filip Balák
Docs Contact:

URL:
Whiteboard:
Keywords:

Depends On:
Blocks:	1503137
	Show dependency tree / graph

Reported:	2018-04-10 02:14 EDT by Lubos Trilety
Modified:	2018-09-04 03:04 EDT (History)
CC List:	6 users (show)

See Also:
Fixed In Version:	tendrl-commons-1.6.3-3.el7rhgs
Doc Type:	If docs needed, set a value
Doc Text:
Story Points:	---
Clone Of:
Environment:
Last Closed:	2018-09-04 03:03:46 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)
completed/processing times (79.42 KB, image/png) 2018-04-10 02:14 EDT, Lubos Trilety	no flags	Details
Add an attachment (proposed patch, testcase, etc.)

External Trackers
Tracker	ID	Priority	Status	Summary	Last Updated
Github	Tendrl/commons/pull/936	None	None	None	2018-04-24 07:33 EDT
Red Hat Product Errata	RHSA-2018:2616	None	None	None	2018-09-04 03:04 EDT

Groups: None (edit)

Description Lubos Trilety 2018-04-10 02:14:25 EDT

Created attachment 1419696 [details]
completed/processing times

Description of problem:
For any profiling task api dooesn't provide updated_at field, which leads to
01 Jan 1970 01:00:00
completed or processing time on UI side.

Example of API response:
job_id	3095ab37-f57d-43a3-949f-86140f0f6cb3
status	finished
flow	EnableDisableVolumeProfiling
parameters	{…}
created_at	2018-04-09T12:00:09Z
updated_at	null
status_url	/jobs/3095ab37-f57d-43a3-949f-86140f0f6cb3/status
messages_url	/jobs/3095ab37-f57d-43a3-949f-86140f0f6cb3/messages
output_url	/jobs/3095ab37-f57d-43a3-949f-86140f0f6cb3/output
errors	null


Version-Release number of selected component (if applicable):
tendrl-ansible-1.6.1-3.el7rhgs.noarch
tendrl-ui-1.6.1-3.el7rhgs.noarch
tendrl-selinux-1.5.4-2.el7rhgs.noarch
tendrl-commons-1.6.1-3.el7rhgs.noarch
tendrl-api-1.6.1-3.el7rhgs.noarch
tendrl-api-httpd-1.6.1-3.el7rhgs.noarch
tendrl-monitoring-integration-1.6.1-3.el7rhgs.noarch
tendrl-grafana-selinux-1.5.4-2.el7rhgs.noarch
tendrl-notifier-1.6.0-1.el7rhgs.noarch
tendrl-node-agent-1.6.1-3.el7rhgs.noarch
tendrl-grafana-plugins-1.6.1-3.el7rhgs.noarch

How reproducible:
100%

Steps to Reproduce:
1. Import cluster
2. Enable/disable profiling for a volume/cluster
3.

Actual results:
The Completed/Processing time displayed on UI is as follows
01 Jan 1970 01:00:00

Expected results:
There should be some correct time displayed.

Additional info:
See profiling tasks times on attached screenshot

Comment 1 Martin Bukatovic 2018-04-13 12:08:39 EDT

This affects Expand operation as well, as can be seen in screenshot 5 in BZ 1566181:

https://bugzilla.redhat.com/attachment.cgi?id=1420507

Comment 3 Nishanth Thomas 2018-04-21 00:11:43 EDT

@shubhendu, does this field populated in etcd

Comment 7 gowtham 2018-04-24 07:33:19 EDT

This is fixed

Comment 9 Filip Balák 2018-05-18 06:22:25 EDT

This seems to be fixed for profiling and expand related tasks. --> VERIFIED

Tested with:
tendrl-ansible-1.6.3-3.el7rhgs.noarch
tendrl-api-1.6.3-3.el7rhgs.noarch
tendrl-api-httpd-1.6.3-3.el7rhgs.noarch
tendrl-commons-1.6.3-4.el7rhgs.noarch
tendrl-grafana-plugins-1.6.3-2.el7rhgs.noarch
tendrl-grafana-selinux-1.5.4-2.el7rhgs.noarch
tendrl-monitoring-integration-1.6.3-2.el7rhgs.noarch
tendrl-node-agent-1.6.3-4.el7rhgs.noarch
tendrl-notifier-1.6.3-2.el7rhgs.noarch
tendrl-selinux-1.5.4-2.el7rhgs.noarch
tendrl-ui-1.6.3-1.el7rhgs.noarch

Comment 11 errata-xmlrpc 2018-09-04 03:03:46 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/RHSA-2018:2616

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