This bug has been migrated to another issue tracking site. It has been closed here and may no longer be being monitored.

If you would like to get updates for this issue, or to participate in it, you may do so at Red Hat Issue Tracker .
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 2131711 - New host details UI, error status results in overall green status
Summary: New host details UI, error status results in overall green status
Keywords:
Status: CLOSED MIGRATED
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Hosts
Version: 6.12.0
Hardware: Unspecified
OS: Unspecified
high
medium
Target Milestone: stream
Assignee: satellite6-bugs
QA Contact: Lukáš Hellebrandt
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-10-03 12:16 UTC by Peter Dragun
Modified: 2024-06-06 12:35 UTC (History)
3 users (show)

Fixed In Version: rubygem-foreman_remote_execution-13.0.0
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2024-06-06 12:35:03 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)
screenshot (11.44 KB, image/png)
2022-10-03 12:16 UTC, Peter Dragun 		no flags Details
View All


Links
System ID Private Priority Status Summary Last Updated
Foreman Issue Tracker 36952 0 Normal Closed Host Status is not updated 2024-03-06 09:34:30 UTC
Red Hat Issue Tracker   SAT-15089 0 None Migrated None 2024-06-06 12:35:01 UTC

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.
Note You need to log in before you can comment on or make changes to this bug.