第11章 Managing Errata

1. Navigate to Content > 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 check box is selected by default to view only errata applicable to the selected repository. Select the Installable check box 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

     検索に使用できるパラメーターの一覧は、表11.1「Parameters Available for Errata Search」 を参照してください。適用可能な演算子の一覧は、『Red Hat Satellite の管理』の「詳細な検索に対してサポートされる演算子」を参照してください。入力時に自動サジェスト機能が利用できます。and 演算子と or 演算子を使用してクエリーを組み合わせることもできます。たとえば、kernel パッケージに関するセキュリティーアドバイザリーのみを表示するには、以下を入力します。

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

Procedure

1. In the Satellite web UI, navigate to Content > Content Views and select a Content View that you want to use for applying errata.
2. Yum コンテンツ > フィルターに移動し、新規フィルターをクリックします。
3. In the Name field, enter Errata Filter.
4. From the Content Type list, select Erratum - Date and Type.
5. From the Inclusion Type list, select Exclude.
6. In the Description field, enter Exclude errata items from YYYY-MM-DD.
7. 保存をクリックします。
8. For Errata Type, select the check boxes of errata types you want to exclude. For example, select the Enhancement and Bugfix check boxes and clear the Security check box to exclude enhancement and bugfix errata after certain date, but include all the security errata.

9. For Date Type, select one of two check boxes:

   • Issued On for the issued date of the erratum.
   • Updated On for the date of the erratum’s last update.
10. Select the Start Date to exclude all errata on or after the selected date.
11. Leave the End Date field blank.
12. 保存をクリックします。
13. Click Publish New Version to publish the resulting repository.
14. Enter Adding errata filter in the Description field.

15. 保存をクリックします。

    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.

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

For CLI Users

1. Create a filter for the errata:

   # hammer content-view filter create --name "Filter Name" \
   --description "Exclude errata items from the YYYY-MM-DD" \
   --content-view "CV Name" --organization "Default 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 --start-date "YYYY-MM-DD" \
   --content-view "CV Name" --content-view-filter="Filter Name" \
   --organization "Default Organization" --types=security,enhancement,bugfix

3. Publish the Content View:

   # hammer content-view publish --name "CV Name" \
   --organization "Default 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 "CV Name" \
   --organization "Default Organization" \
   --to-lifecycle-environment "Lifecycle Environment Name"

1. Satellite Web UI で、コンテンツ > エラータ に移動します。
2. エラータ の一覧から、適用するエラータの名前をクリックします。
3. エラータを適用するコンテンツホストを選択し、ホストに適用 をクリックします。これにより、コンテンツビューの増分更新が作成されます。
4. エラータをコンテンツホストに適用する場合は、公開直後にコンテンツホストにエラータを適用する チェックボックスを選択します。
5. 確認 をクリックして、エラータを適用します。

For CLI Users

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. コンテンツビューバージョンに単一のエラータを適用します。コンマ区切りのリストとして、さらに ID を追加できます。

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

1. On Satellite, list all errata for the host:

   # hammer host errata list \
   --host client.example.com

2. エラータが含まれるモジュールのストリームを検索します。

   # hammer erratum info --id ERRATUM_ID

3. On the host, update the module stream:

   # yum update Module_Stream_Name

1. In the Satellite web UI, navigate to Hosts > Content Hosts and select the host you want to apply errata to.
2. Navigate to the Errata tab to see the list of errata.
3. 適用するエラータを選択し、Apply Selected (選択した項目を適用) をクリックします。確認画面で、適用 をクリックします。
4. After the task to update all packages associated with the selected errata completes, click the Details tab to view the updated packages.

1. List all errata for the host:

   # hammer host errata list \
   --host client.example.com

2. ホストに最新のエラータを適用します。エラータ ID を使用して適用するエラータを特定します。

   # hammer host errata apply --host "Host Name" \
   --errata-ids ERRATUM_ID1,ERRATUM_ID2...

Procedure

1. Navigate to Content > Errata.
2. Click the name of an erratum you want to apply.
3. Click to Content Hosts tab.
4. エラータの適用先のホストを選択し、ホストへの適用 をクリックします。
5. Click Confirm.

1. List all installable errata:

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

2. Select the erratum you want to use and list the hosts that this erratum is applicable to:

   # hammer host list \
   --search "applicable_errata = ERRATUM_ID" \
   --organization "Default Organization"

3. Apply the errata to a single host:

   # hammer host errata apply \
   --host client.example.com \
   --organization "Default Organization" \
   --errata-ids ERRATUM_ID1,ERRATUM_ID2...

4. Enter the following command for each host and replace $HOST with the name of the host for each execution.

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