Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
Red Hat Satellite engineering is moving the tracking of its product development work on Satellite to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "Satellite project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs will be migrated starting at the end of May. If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "Satellite project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/SAT-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Descriptionsthirugn@redhat.com
2015-03-11 20:21:08 UTC
Created attachment 1000654[details]
Foreman task page for a failed task
Description of problem:
Foreman tasks which are stopped with failures should be in orange vs. blue
Version-Release number of selected component (if applicable):
Satellite-6.1.0-RHEL-6-20150303.0
How reproducible:
Always
Steps to Reproduce:
1. Go to Monitor -> Tasks
2. Review a foreman task which is stopped but failed (One way to reproduce this is to upload the same manifest twice)
Actual results:
The task Result = warning, and the progress shows 100% with blue color. This is not very intuitive to note that there is a failure (screenshot attached)
Expected results:
The progress should show 100% with Orange color.
Additional info:
Moving to POST since upstream bug http://projects.theforeman.org/issues/9725 has been closed
-------------
Justin Sherrill
Applied in changeset commit:ef3e551fb1e99ba9eac1c201e60fc6bf9ee76e57.
Comment 6sthirugn@redhat.com
2015-03-23 14:32:12 UTC
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-2015:1592
Created attachment 1000654 [details] Foreman task page for a failed task Description of problem: Foreman tasks which are stopped with failures should be in orange vs. blue Version-Release number of selected component (if applicable): Satellite-6.1.0-RHEL-6-20150303.0 How reproducible: Always Steps to Reproduce: 1. Go to Monitor -> Tasks 2. Review a foreman task which is stopped but failed (One way to reproduce this is to upload the same manifest twice) Actual results: The task Result = warning, and the progress shows 100% with blue color. This is not very intuitive to note that there is a failure (screenshot attached) Expected results: The progress should show 100% with Orange color. Additional info: