Description of problem ====================== When RHSC 2.0 task is killed by console itself because of timeout, in a Task Details page for the task, the message reporting this has the following format: > Force Stop. Task: TASK_UID explicitly stopped. This is the only information on the task detail page related to the failure caused by the timeout. The problem with the such error message is that it's not completely clear that: * the task was killed by console itself (and not by a user or some other component) * the reason for the force stop of the task is a timeout, the task took longer than expected Version-Release =============== rhscon-ceph-0.0.36-1.el7scon.x86_64 rhscon-core-selinux-0.0.36-1.el7scon.noarch rhscon-core-0.0.36-1.el7scon.x86_64 rhscon-ui-0.0.50-1.el7scon.noarch How reproducible ================ 100% Steps to Reproduce ================== 1. Install RHSC 2.0 following the documentation. 2. Start a task (eg. Initialize Node, Create Cluster) so that it will timeout. 3. Check the Task Details page when the task fails. Actual results ============== On the task detail page of the failed task, the last entry states: > Force Stop. Task: a46cdd63-2f2e-403d-8cdc-ddb5c42fd506 explicitly stopped. Expected results ================ On the task detail page of the failed task, the last entry states: > Task a46cdd63-2f2e-403d-8cdc-ddb5c42fd506 has been killed after timeout I'm not proposing a particular replacement, as I'm neither native speaker or ui designer. That said, It should be clear that: * the task was killed/stopped by console itself * console did this because of timeout
Created attachment 1184086 [details] screenshot 1: task details page after a timeout
Could the design team propose suitable replacement for the current message here?
I am changing the message as "Force Stop. Task: <id> explicitly stopped due to timeout."
(In reply to Shubhendu Tripathi from comment #3) > I am changing the message as "Force Stop. Task: <id> explicitly stopped due > to timeout." Since it seems that the format of the message has been decided and it looks ok, I'm removing the needinfo flag.
Tested with ceph-ansible-1.0.5-32.el7scon.noarch ceph-installer-1.0.14-1.el7scon.noarch rhscon-ceph-0.0.39-1.el7scon.x86_64 rhscon-core-0.0.39-1.el7scon.x86_64 rhscon-core-selinux-0.0.39-1.el7scon.noarch rhscon-ui-0.0.51-1.el7scon.noarch and task ID is missing in error message: "Force Stop. Task explicitly stopped due to timeout." -->ASSIGNED
Martin, so the message comes from two different places in USM. In one place from where this got generated we dont have task id available and so not in the message. Also this BZ was just to make message more clearer which was already existing. This is actually not an issue should be verified as its as per the code in USM.
Closing as Verified after discussion.
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/RHEA-2016:1754