Chapter 10. Managing errata

Procedure

1. In the Satellite web UI, navigate to Content > Content Types > Errata to view the list of available errata.

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

   • Select the repository to be inspected from the list. All Repositories is selected by default.
   • The Applicable checkbox is selected by default to view only applicable errata in the selected repository. Select the Installable checkbox to view only errata marked as installable.

   • To search the table of errata, type the query in the Search field in the form of:

     parameter operator value

     See Section 10.3, “Parameters available for errata search” for the list of parameters available for search. Find the list of applicable operators in Supported Operators for Granular Search in Administering Red Hat Satellite. Automatic suggestion works as you type. You can also combine queries with the use of and and or operators. For example, to display only security advisories related to the kernel package, type:

     type = security and package_name = kernel

     Press Enter to start the search.

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

   • The Details tab contains the description of the updated package as well as documentation of important fixes and enhancements provided by the update.
   • On the Content Hosts tab, you can apply the erratum to selected content hosts as described in Section 10.11, “Applying errata to multiple hosts”.
   • The Repositories tab lists repositories that already contain the erratum. You can filter repositories by the environment and content view, and search for them by the repository name.

1. In the Satellite web UI, navigate to Hosts > All Hosts and select the host you require.
2. 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.
3. On the new Host page, select the Content tab.
4. On the Content page select the Errata tab.
5. The page displays installable errata for the chosen host.
6. Click the checkbox for any errata you wish to install.
7. Select Apply via Remote Execution to use Remote Execution, or Apply via customized remote execution if you want to customize the remote execution.
8. Click Submit.

Procedure

1. In the Satellite web UI, navigate to Hosts > All Hosts and select the host you require.
2. If there are errata associated with the host, they are displayed in an Installable Errata card on the new Host page.
3. On the Content tab, Errata displays installable errata for the chosen host.
4. Click the checkbox for any errata you wish to install.
5. 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.
6. Click Submit.

Procedure

1. In the Satellite web UI, navigate to Hosts > Templates > Job Templates.
2. Click Create Template.

3. 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:

   • Append custom pre to the name of a template to run code before applying errata on hosts.
   • Append custom post to the name of a template to run code after applying errata on hosts.

   If your template is called Install Errata - Katello Ansible Default, name your template Install Errata - Katello Ansible Default custom pre or Install Errata - Katello Ansible Default custom post.

4. On the Type tab, select Snippet.
5. Click Submit to create your custom snippet.

CLI procedure

1. Create a plain text file that contains your custom snippet.

2. 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

Procedure

1. In the Satellite web UI, navigate to Content > Lifecycle > Content Views.
2. Select a content view that you want to use for applying errata.
3. Select Yum Content > Filters and click New Filter.
4. In the Name field, enter Errata Filter.
5. From the Content Type list, select Erratum – Date and Type.
6. From the Inclusion Type list, select Exclude.
7. In the Description field, enter Exclude errata items from YYYY-MM-DD.
8. Click Save.
9. 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.

10. For Date Type, select one of two checkboxes:

    • Issued On for the issued date of the erratum.
    • Updated On for the date of the erratum’s last update.
11. Select the Start Date to exclude all errata on or after the selected date.
12. Leave the End Date field blank.
13. Click Save.
14. Click Publish New Version to publish the resulting repository.
15. Enter Adding errata filter in the Description field.

16. Click Save.

    When the content view completes publication, notice the Content column reports a reduced number of packages and errata from the initial repository. This means the filter successfully excluded the all non-security errata from the last year.

17. Click the Versions tab.
18. Click Promote to the right of the published version.
19. Select the environments you want to promote the content view version to.
20. In the Description field, enter the description for promoting.
21. Click Promote Version to promote this content view version across the required environments.

CLI procedure

1. 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"

2. 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

3. Publish the content view:

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

4. 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"

Procedure

1. In the Satellite web UI, navigate to Content > Content Types > Errata.
2. From the Errata list, click the name of the errata that you want to apply.
3. 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.
4. If you want to apply the errata to the content host, select the Apply Errata to Content Hosts immediately after publishing checkbox.
5. Click Confirm to apply the errata.

CLI procedure

1. List the errata and its corresponding IDs:

   # hammer erratum list

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

   # hammer content-view version list

3. 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

Procedure

1. In the Satellite web UI, navigate to Content > Content Types > Errata.
2. Click the name of an erratum you want to apply.
3. Click to Content Hosts tab.
4. Select the hosts you want to apply errata to and click Apply to Hosts.
5. Click Confirm.

CLI procedure

1. List all installable errata:

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

2. Apply one of the errata to multiple hosts:

   Using Remote Execution

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

   The following Bash script applies an erratum to each host for which this erratum is available:

   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

   This command identifies all hosts with erratum_IDs as an applicable erratum and then applies the erratum to each host.

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

   # hammer task list

4. View the state of a selected task:

   # hammer task progress --id task_ID