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 2070732 - Use more accurate messaging when host statuses are cleared
Summary: Use more accurate messaging when host statuses are cleared
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: Jeremy Lenz
QA Contact: Peter Dragun
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-03-31 19:15 UTC by tstrych
Modified: 2022-11-16 13:34 UTC (History)
3 users (show)

Fixed In Version: foreman-3.3.0.12-1
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
Foreman Issue Tracker 35206 0 Normal New new host ui details, UX RFE on host status 2022-07-12 14:08:34 UTC
Red Hat Issue Tracker SAT-11534 0 None None None 2022-07-12 14:15:49 UTC
Red Hat Product Errata RHSA-2022:8506 0 None None None 2022-11-16 13:34:01 UTC

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


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