Chapter 13. Making errata available through content views

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

     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 install installable errata on selected 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 > Lifecycle > Content Views.
2. Select a content view that you want to use for applying errata.
3. On the Filters tab, click Create Filter.
4. In the Name field, enter Errata Filter.
5. From the Content Type list, select Errata – by date range.
6. Select Exclude filter.
7. Optional: In the Description field, enter Exclude errata items from YYYY-MM-DD.
8. Click Create filter.
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:

    • Updated from for the date of the last update of the erratum.
    • Issued from for the issued date of the erratum.
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.

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 a Start Date:

   $ 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 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 host, select the Apply Errata to Content Hosts immediately after publishing checkbox.
5. Click Confirm to apply the errata.

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 My_Content_View_Version_ID \
   --errata-ids My_Erratum_ID_1,My_Erratum_ID_2

Procedure

1. Allow the MCP server to trigger content view actions:

   $ podman run --interactive --tty --publish 127.0.0.1:8080:8080 \
     --volume Path_to_My_CA_Bundle:/app/ca.pem:ro,Z \
     registry.redhat.io/satellite/foreman-mcp-server-rhel9:6.18 \
     --foreman-url https://satellite.example.com \
     --allowed-cv-actions "incremental_update"

   For more information, see Deploying the MCP server for Satellite in Managing hosts.

2. Type a prompt in your AI application to list applicable errata:

   Show a list of applicable errata on my Satellite.

3. The MCP server will return a list of applicable errata to the AI application. Review the information.
4. The Satellite MCP server provides a prompt named Add Errata to Content Views, which you can use to perform an incremental update of a content view. Refer to the documentation of your AI application to find more about how to use MCP server prompts. Review all the steps that the AI application performs.