Replace 'content host' with 'host' #4583
Conversation
github-actions
bot
added
Needs tech review
| * Use errata to add patches for security issues to a frozen set of content without unnecessarily updating other unaffected packages. | ||
| * Automate errata management by using a Hammer script or an {ansible-docs-url}[Ansible Playbook]. | ||
| * View errata on the content hosts page and compare the errata of the current content view environment to the Library lifecycle environment, which contains the latest synchronized packages. | ||
| * View errata on the hosts page and compare the errata of the current content view environment to the Library lifecycle environment, which contains the latest synchronized packages. |
There was a problem hiding this comment.
| * View errata on the hosts page and compare the errata of the current content view environment to the Library lifecycle environment, which contains the latest synchronized packages. | |
| * View errata on the *All Hosts* page and compare the errata of the current content view environment to the Library lifecycle environment, which contains the latest synchronized packages. |
I'm not sure if one can actually compare errata between CVEnvs on the All Hosts page?
Perhaps this practice will have to be rewritten more thoroughly.
cc @jeremylenz
There was a problem hiding this comment.
I think "content hosts page" meant the detail page. You can compare errata on the new host details page > Content tab > Errata tab. Then use the toggle group to select "Applicable" / "Installable". (Applicable corresponds to Library, while Installable only shows errata in the host's content view environments that is available to install.) Note that you will not see the toggle group if the host is subscribed to Library and Default Organization View.
There was a problem hiding this comment.
Shouldn't there be a separate procedure for that? This is too much detail to include in best practices.
The best I can do for now is this.
There was a problem hiding this comment.
Shouldn't there be a separate procedure for that?
That's fair. This was written ages ago, so I'm sure another look is long overdue.
There was a problem hiding this comment.
I'm still considering this.
guides/common/modules/proc_enabling-custom-repositories-on-content-hosts.adoc
Outdated
Show resolved
Hide resolved
guides/common/modules/ref_best-practices-for-patching-content-hosts.adoc
Show resolved
Hide resolved
Co-authored-by: Jeremy Lenz <jlenz@redhat.com>
Lennonka
force-pushed
the
replace-content-host-with-host
branch
from
f1bb03e to
3e27ff5
Compare
|
Rebased + updated |
3 participants
What changes are you introducing?
Replacing 'content host' with just 'host'
Why are you introducing these changes? (Explanation, links to references, issues, etc.)
Moving away from legacy terminology
SAT-41431 (public)
Anything else to add? (Considerations, potential downsides, alternative solutions you have explored, etc.)
Contributor checklists
Please cherry-pick my commits into: None