Bug 2131711

Summary: New host details UI, error status results in overall green status
Product: Red Hat Satellite Reporter: Peter Dragun <pdragun>
Component: HostsAssignee: satellite6-bugs <satellite6-bugs>
Status: CLOSED MIGRATED QA Contact: Lukáš Hellebrandt <lhellebr>
Severity: medium Docs Contact:
Priority: high    
Version: 6.12.0CC: aruzicka, inecas, lhellebr
Target Milestone: streamKeywords: MigratedToJIRA, Triaged, UserExperience
Target Release: Unused   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: rubygem-foreman_remote_execution-13.0.0 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2024-06-06 12:35:03 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:
Attachments:
Description Flags
screenshot none

Description Peter Dragun 2022-10-03 12:16:04 UTC
Created attachment 1915710 [details]
screenshot

Description of problem:
Overall status is green even if one error occurred. All statuses were cleared before the error.
By overall status I mean the one next to `Host status` card title and the hostname.
See attached screenshot.

Version-Release number of selected component (if applicable):


How reproducible:
always

Steps to Reproduce:
1. Clear all hosts statuses
2. Make sure that the 'Host status' card says All statuses cleared
3. Create one error status: e.g. run rex without adding rex key

Actual results:
Overall status with the green checkmark.

Expected results:
Overall status should be an error as there was an error status in rex.

Additional info:
Errata status: 'All errata up-to-date'

Comment 2 Adam Ruzicka 2023-11-27 14:39:49 UTC
It seems that, at least in the case of REX, we don't refresh the global status when updating the rex status.

Comment 3 Eric Helms 2024-06-06 12:35:03 UTC
This BZ has been automatically migrated to the issues.redhat.com Red Hat Issue Tracker. All future work related to this report will be managed there.

Due to differences in account names between systems, some fields were not replicated.  Be sure to add yourself to Jira issue's "Watchers" field to continue receiving updates and add others to the "Need Info From" field to continue requesting information.

To find the migrated issue, look in the "Links" section for a direct link to the new issue location. The issue key will have an icon of 2 footprints next to it, and begin with "SAT-" followed by an integer.  You can also find this issue by visiting https://issues.redhat.com/issues/?jql= and searching the "Bugzilla Bug" field for this BZ's number, e.g. a search like:

"Bugzilla Bug" = 1234567

In the event you have trouble locating or viewing this issue, you can file an issue by sending mail to rh-issues. You can also visit https://access.redhat.com/articles/7032570 for general account information.