Bug 2070732

Summary: Use more accurate messaging when host statuses are cleared
Product: Red Hat Satellite Reporter: tstrych
Component: HostsAssignee: Jeremy Lenz <jlenz>
Status: CLOSED ERRATA QA Contact: Peter Dragun <pdragun>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 6.11.0CC: inecas, jlenz, pcreech
Target Milestone: 6.12.0Keywords: EasyFix, FutureFeature, Triaged, UserExperience
Target Release: Unused   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: foreman-3.3.0.12-1 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2022-11-16 13:33:45 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:

Description tstrych 2022-03-31 19:15:11 UTC 
Created attachment 1869788 [details]
pict 2. manage host's statuses are N/A

Description of problem:
This BZ is part of  BZ 2070615, precisely scenario A

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.


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

How reproducible:
Always

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"
Comment 7 Jeremy Lenz 2022-07-12 14:06:31 UTC 
Per discussion with UX:

1) Use Patternfly 4 "BanIcon"
2) Use the message wording "All statuses cleared"
(Leave "All statuses OK" unchanged for when they are actually OK and not cleared.)
Comment 8 Jeremy Lenz 2022-07-12 14:08:33 UTC 
Created redmine issue https://projects.theforeman.org/issues/35206 from this bug
Comment 9 Bryan Kearney 2022-09-09 20:04:06 UTC 
Upstream bug assigned to jlenz
Comment 10 Bryan Kearney 2022-09-09 20:04:09 UTC 
Upstream bug assigned to jlenz
Comment 13 Peter Dragun 2022-10-03 12:02:03 UTC 
Verified on Sat 6.12 snap 13
Comment 17 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