Bug 1686855 - Task messages are not informative
Summary: Task messages are not informative
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Gluster Storage
Classification: Red Hat Storage
Component: web-admin-tendrl-node-agent
Version: rhgs-3.4
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: ---
: ---
Assignee: Timothy Asir
QA Contact: sds-qe-bugs
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-03-08 14:14 UTC by Filip Balák
Modified: 2020-02-07 08:20 UTC (History)
2 users (show)

Fixed In Version: tendrl-commons-1.6.3-18.el7rhgs.noarch
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-02-07 08:20:24 UTC
Embargoed:


Attachments (Terms of Use)
Unmanage task detail (104.13 KB, image/png)
2019-03-08 14:14 UTC, Filip Balák
no flags Details

Description Filip Balák 2019-03-08 14:14:13 UTC
Created attachment 1542117 [details]
Unmanage task detail

Description of problem:
During cluster import and cluster unmanage jobs are shown several times messages like:
Starting Job <some-job-id>
Job (<some-job-id>) for <task> finished.

User is not informed about what job is actually being executed or what is happening.

Version-Release number of selected component (if applicable):
tendrl-node-agent-1.6.3-18.el7rhgs.noarch
tendrl-grafana-selinux-1.5.4-3.el7rhgs.noarch
tendrl-notifier-1.6.3-4.el7rhgs.noarch
tendrl-selinux-1.5.4-3.el7rhgs.noarch
tendrl-api-1.6.3-13.el7rhgs.noarch
tendrl-api-httpd-1.6.3-13.el7rhgs.noarch
tendrl-grafana-plugins-1.6.3-21.el7rhgs.noarch
tendrl-ansible-1.6.3-11.el7rhgs.noarch
tendrl-commons-1.6.3-17.el7rhgs.noarch
tendrl-ui-1.6.3-15.el7rhgs.noarch
tendrl-monitoring-integration-1.6.3-21.el7rhgs.noarch

How reproducible:
100%

Steps to Reproduce:
1. Install Tendrl and create Gluster cluster.
2. Import cluster into Tendrl.
3. Open detail of the job and save the output.
4. Expand imported cluster.
5. Open detail of the job and save the output.
6. Unmanage the cluster.
7. Open detail of the job and save the output.

Actual results:
In saved outputs are several messages like:
Starting Job <some-job-id>
Job (<some-job-id>) for <task> finished.

Expected results:
Instead there should be more specific messages about the job that is currently in progress/finished.

Additional info:


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