Problem Statement

Users who use non-EL systems frequently run into the issue of errata applicability returning a warning or error status, causing the entire host status to show yellow instead of green. I'd like for users to be able to disable certain host statuses from influencing the overall host status calculation, on a host-by-host basis.

User Experience & Workflow

A user should be able to quickly verify host status for hosts while ignoring components they do not use or components they know will fail. Optional host status components should be obviously expressed so that a user knows if components aren't being taken into account.

Requirements

• Add the ability to set each host status component as optional.
• Exclude optional host statuses from overall host status calculation.
• On the "Manage all statuses" modal, add another option to the status' kebab menu called "Mark as optional". For statuses with the optional flag, add the option "Mark as required".
• On the "Manage all statuses" modal, bold the names of required host status components and add the string " (optional)" to optional host status components.
• On the host status card, component counts marked as optional should be displayed in parens. For example 3 passing and 1 optional error should look like this: ✅ 3  ⚠️ 0 (1)

Business Impact

Non-EL users would continue to ignore the host status metrics because they will always show issues. This RFE will help drive adoption and trust for host status.

Open Questions:

Can we determine if this machine shouldn't have errata calculations and not mess up applicability 

should this be a bug ?