Managing errata

In the orcharhino management UI, navigate to Content > Content Types > Errata to view the list of available errata.

Use the filtering tools at the top of the page to limit the number of displayed errata:

Click the Errata ID of the erratum you want to inspect:

In the orcharhino management UI, navigate to Hosts > All Hosts and select the host you require.

If there are errata associated with the host, an Installable Errata card on the new Host page displays an interactive pie chart showing a breakdown of the security advisories, bugfixes, and enhancements.

On the new Host page, select the Content tab.

On the Content page select the Errata tab.

The page displays installable errata for the chosen host.

Click the checkbox for any errata you wish to install.

Select Apply via Remote Execution to use Remote Execution, or Apply via customized remote execution if you want to customize the remote execution.

Click Submit.

In the orcharhino management UI, navigate to Hosts > All Hosts and select the host you require.

If there are errata associated with the host, they are displayed in an Installable Errata card on the new Host page.

On the Content tab, Errata displays installable errata for the chosen host.

Click the checkbox for any errata you wish to install.

Using the vertical ellipsis icon next to the errata you want to add to the host, select Apply via Remote Execution to use Remote Execution. Select Apply via customized remote execution if you want to customize the remote execution.

Click Submit.

In the orcharhino management UI, navigate to Hosts > Templates > Job Templates.

Click Create Template.

In the Name field, enter a name for your custom snippet. The name must start with the name of a template that supports custom snippets:

On the Type tab, select Snippet.

Click Submit to create your custom snippet.

Create a plain text file that contains your custom snippet.

Create the template using hammer:

# hammer template create \
--file "~/My_Snippet" \
--locations "My_Location" \
--name "My_Template_Name_custom_pre" \
--organizations "_My_Organization" \
--type snippet

In the orcharhino management UI, navigate to Content > Lifecycle > Content Views.

Select a content view that you want to use for applying errata.

Select Yum Content > Filters and click New Filter.

In the Name field, enter Errata Filter.

From the Content Type list, select Erratum – Date and Type.

From the Inclusion Type list, select Exclude.

In the Description field, enter Exclude errata items from YYYY-MM-DD.

Click Save.

For Errata Type, select the checkboxes of errata types you want to exclude. For example, select the Enhancement and Bugfix checkboxes and clear the Security checkbox to exclude enhancement and bugfix errata after certain date, but include all the security errata.

For Date Type, select one of two checkboxes:

Select the Start Date to exclude all errata on or after the selected date.

Leave the End Date field blank.

Click Save.

Click Publish New Version to publish the resulting repository.

Enter Adding errata filter in the Description field.

Click Save.

Click the Versions tab.

Click Promote to the right of the published version.

Select the environments you want to promote the content view version to.

In the Description field, enter the description for promoting.

Click Promote Version to promote this content view version across the required environments.

Create a filter for the errata:

# hammer content-view filter create \
--content-view "My_Content_View" \
--description "Exclude errata items from the YYYY-MM-DD" \
--name "My_Filter_Name" \
--organization "My_Organization" \
--type "erratum"

Create a filter rule to exclude all errata on or after the Start Date that you want to set:

# hammer content-view filter rule create \
--content-view "My_Content_View" \
--content-view-filter="My_Content_View_Filter" \
--organization "My_Organization" \
--start-date "YYYY-MM-DD" \
--types=security,enhancement,bugfix

Publish the content view:

# hammer content-view publish \
--name "My_Content_View" \
--organization "My_Organization"

Promote the content view to the lifecycle environment so that the included errata are available to that lifecycle environment:

# hammer content-view version promote \
--content-view "My_Content_View" \
--organization "My_Organization" \
--to-lifecycle-environment "My_Lifecycle_Environment"

In the orcharhino management UI, navigate to Content > Content Types > Errata.

From the Errata list, click the name of the errata that you want to apply.

Select the content hosts that you want to apply the errata to, and click Apply to Hosts. This creates the incremental update to the content view.

If you want to apply the errata to the content host, select the Apply Errata to Content Hosts immediately after publishing checkbox.

Click Confirm to apply the errata.

List the errata and its corresponding IDs:

# hammer erratum list

List the different content-view versions and the corresponding IDs:

# hammer content-view version list

Apply a single erratum to content-view version. You can add more IDs in a comma-separated list.

# hammer content-view version incremental-update \
--content-view-version-id 319 --errata-ids 34068b

In the orcharhino management UI, navigate to Content > Content Types > Errata.

Click the name of an erratum you want to apply.

Click to Content Hosts tab.

Select the hosts you want to apply errata to and click Apply to Hosts.

Click Confirm.

List all installable errata:

# hammer erratum list \
--errata-restrict-installable true \
--organization "Default Organization"

Apply one of the errata to multiple hosts:

# hammer job-invocation create \
--feature katello_errata_install \
--inputs errata=ERRATUM_ID \
--search-query "applicable_errata = ERRATUM_ID"

for HOST in hammer --csv --csv-separator "|" host list --search "applicable_errata = ERRATUM_ID" --organization "Default Organization" | tail -n+2 | awk -F "|" '{ print $2 }' ;
do
  echo "== Applying to $HOST ==" ; hammer host errata apply --host $HOST --errata-ids ERRATUM_ID1,ERRATUM_ID2 ;
done

To see if an erratum is applied successfully, find the corresponding task in the output of the following command:

# hammer task list

View the state of a selected task:

# hammer task progress --id task_ID