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 2264890 - [RFE] Add Option to disable/enable Host status for everyhost status plugin.
Summary: [RFE] Add Option to disable/enable Host status for everyhost status plugin.
Keywords:
Status: CLOSED MIGRATED
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Hosts
Version: 6.14.1
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: Unspecified
Assignee: satellite6-bugs
QA Contact: Satellite QE Team
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2024-02-19 14:21 UTC by Satyajit Das
Modified: 2024-06-06 17:03 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2024-06-06 17:03:22 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker   SAT-23385 0 None Migrated None 2024-06-06 17:03:21 UTC

Description Satyajit Das 2024-02-19 14:21:44 UTC 
1. Proposed title of this feature request

Add an Option to disable/enable Host status for every host status plugin.

2. What is the nature and description of the request?

The customer uses satellite to monitor the host status however for a few pluin the host status always remains in error status, the customer is requesting for a customizable option to enable or disable the status.

For ex.

Compliance reports always remain in incompliant status however those failed checks cannot be fixed due to the nature of the check.

3. How would the customer like to achieve this? (List the functional requirements here) 

Should have a toggle button available in the host status page to disable/enable the Host status plugin.


4. Is there an existing RFE upstream or in Red Hat Bugzilla?

N/A
5. Would the customer be able to assist in testing this functionality if implemented?

Yes, they have a test Satellite
Comment 2 Adam Ruzicka 2024-02-19 14:41:44 UTC 
> for every host status plugin

How would you define a "host status plugin"? I'm a bit confused by the word "plugin"

> Should have a toggle button available in the host status page to disable/enable the Host status plugin.

Am I reading it right that they would like to see this work on a per-host level? As in you go into that page and you say "compliance status is never relevant for foo.example.com" or was it meant more generally that on this page you would mark a host status as ignored for all hosts across all organizations?
Comment 6 Eric Helms 2024-06-06 17:03:22 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.