Bug 1686855

Summary: Task messages are not informative
Product: [Red Hat Storage] Red Hat Gluster Storage Reporter: Filip Balák <fbalak>
Component: web-admin-tendrl-node-agentAssignee: Timothy Asir <tjeyasin>
Status: CLOSED CURRENTRELEASE QA Contact: sds-qe-bugs
Severity: medium Docs Contact:
Priority: unspecified    
Version: rhgs-3.4CC: nthomas, rhs-bugs
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: tendrl-commons-1.6.3-18.el7rhgs.noarch Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2020-02-07 08:20:24 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
Unmanage task detail none

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: