When displaying the hosts list, most of the hosts are displayed as in error because “Security errata installable”.
In our current workflow we don’t install errata right away as it might require a reboot.
Is there a way to configure Foreman to discard the errata status in the overall host status as we want to focus on the configuration/puppet status when checking the hosts list ?
You can temporarily clear any host status. In the web UI, host details page, Host status card, click Manage all statuses > then click the vertical ellipsis next to Errata status > Clear.
I think the status may reappear the next time applicability gets recalculated (e.g. host checkin or package action.) But at least this will offer you a way to clear it temporarily.
I am not sure if there is also a way to do it via hammer - check the hammer help.
If you need the errata status to be green without clearing it, your only option is to make sure the errata it needs are not available in the host’s assigned content view environments – or actually apply the errata.
@jeremylenz Thank you for the answer. I think we’ll have to revisit the way we roll out our errata updates.
The issue for us is that we don’t want to necessarily run the updates right away as some may require a reboot - but this is a separate topic for us to figure out.
It may be worth considering changes to your content view / lifecycle environment strategy. Katello’s content views can definitely help here – the whole point of them is to have available exactly what content you want, and not the content you don’t want. If you aren’t already using lifecycle environments, adding them could be a way to accomplish what you want.
