Bug 1560879 – UI should disable the button when button or link is clicked for profiling

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

Bug 1560879 - UI should disable the button when button or link is clicked for profiling

Summary:	UI should disable the button when button or link is clicked for profiling

Status:	CLOSED ERRATA

Aliases:	None

Product:	Red Hat Gluster Storage
Classification:	Red Hat
Component:	web-admin-tendrl-ui (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:	Neha Gupta
QA Contact:	Filip Balák
Docs Contact:

URL:
Whiteboard:
Keywords:

Depends On:
Blocks:	1503137
	Show dependency tree / graph

Reported:	2018-03-27 04:01 EDT by Neha Gupta
Modified:	2018-09-04 03:04 EDT (History)
CC List:	6 users (show)

See Also:
Fixed In Version:	tendrl-ui-1.6.3-2.el7rhgs
Doc Type:	If docs needed, set a value
Doc Text:
Story Points:	---
Clone Of:
Environment:
Last Closed:	2018-09-04 03:03:18 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)
Add an attachment (proposed patch, testcase, etc.)

External Trackers
Tracker	ID	Priority	Status	Summary	Last Updated
Github	Tendrl/ui/issues/890	None	None	None	2018-04-04 23:56 EDT
Red Hat Product Errata	RHSA-2018:2616	None	None	None	2018-09-04 03:04 EDT

Groups: None (edit)

Description Neha Gupta 2018-03-27 04:01:59 EDT

If a user clicks on enable/disable profiling link or button on cluster list or volume list view, UI should disable the link/button and if the API failed for it, it should enable it back. Once next API call response received, link/button should be enabled/disabled based on the API response. If user refreshes the view, again link/button will be enabled/disabled based on the API response

Comment 5 Filip Balák 2018-06-06 09:43:21 EDT

Seems ok. --> VERIFIED

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

Comment 7 errata-xmlrpc 2018-09-04 03:03:18 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.