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.
Bug 2069440 - [RFE] new host ui details, upgrades to host status
Summary: [RFE] new host ui details, upgrades to host status
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Hosts
Version: 6.11.0
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: 6.12.0
Assignee: satellite6-bugs
QA Contact: Peter Dragun
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-03-28 21:31 UTC by tstrych
Modified: 2022-11-16 13:34 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2022-11-16 13:33:45 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker SAT-11644 0 None None None 2022-07-15 13:59:39 UTC
Red Hat Product Errata RHSA-2022:8506 0 None None None 2022-11-16 13:34:01 UTC

Description tstrych 2022-03-28 21:31:52 UTC
Description of problem:

In new host details in overview tab in host status card. 
The user has the ability to remove the shown statuses.
Once the user removes all of them, the overall status is saying
"All statuses are  OK" - picture 1., but when "Manage all statuses" is open 
there is None - picture 2.

Another problematic scenario with these two fields for statuses.
Global status can be Ok, but we can have some warnings. So we will end up with picture 3. When the user can see green at the top (overall) and also yellow or red in the columns (statuses) 


Why does this happen?
There are two statuses, global status and statuses. 
The statuses are removed but global status stays. That's the cause of this problem.

Version-Release number of selected component (if applicable):
sat 6.11 snap 14

How reproducible:
Always

Steps to Reproduce:
scenario A) 
1. Host -> Host detail -> Overview -> Host status 
2. Manage all statuses -> Remove all the statuses

Actual results:
All statuses are  OK

Expected results:
"No status" or "Empty"

scenario B) 
1. Create a host 
2. unsuccessfully run a REX
3. look at Host -> Host detail -> Overview -> Host status  -> 

Actual results:
overall status is green even though there is an error

Expected results:
From UX perspective overall status should not be green if something just went wrong. 

Additional info:
This can be separated into two BZ's.

Comment 4 tstrych 2022-03-31 14:48:38 UTC
After discussion on host details meeting, scenario B) is a valid BZ, 
together with this BZ there is plan to improve host statuses spans, (so icon and number of errors are not so near to each other (ok, warning, error, none), and vertically better aligned )

Comment 5 tstrych 2022-03-31 14:52:54 UTC
in scenario B if REX is passing, remove the key from the authorized keys on the host that is registered to satellite

Comment 6 tstrych 2022-03-31 19:20:50 UTC
after discussion with Amir, branching scenario A to a new different BZ 2070732

Comment 19 Peter Dragun 2022-08-24 13:22:35 UTC
Verified on Sat 6.12 snap 7

Comment 23 errata-xmlrpc 2022-11-16 13:33:45 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 (Important: Satellite 6.12 Release), 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-2022:8506


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