The errata page can be accessed via The Content Menu:
Content > Errata
Errata describe fixes (patches) for packages with known issues. Currently orcharhino supports errata for packages of type RPM as well as deb. Amongst other things, the errata system may be used to perform critical security updates, on software that cannot be updated to it’s newest version for compatibility reasons. Within orcharhino, the addition of errata to a content view, which renders it available for installation, iterates the minor version number of that content view (.1, .2, .3 etc). (See also: Content Views).
The errata page displays a list of all errata currently available through orcharhino’s content management. (That is all the errata, contained in all yum type repositories imported into orcharhino as part of any product).
The errata page includes several filter options, an Apply Errata button, and a list of available errata:
- The drop down repository filter (1) will filter the list of errata (5) to show only those errata, that are present in the selected repository (“All Repositories” by default).
- The Applicable check box (2) will filter the list of errata (5) to show only those errata, that are applicable to one or more content hosts.
- The Installable check box (3) will filter the list of errata (5) to show only those errata, that are applicable to one or more content hosts, and are present in the content host’s lifecycle environment and content view.
- The Apply Errata button (4) (only clickable when at least one erratum from the list of errata (5) is selected) will take you to the apply errata page for the selected errata. (See Applying Errata below).
- Clicking on an erratum in the Errata ID column (6) will take you to the erratum overview page for that erratum. (See Viewing an Erratum below).
- The Type column (7) is of particular importance to the evaluation of available errata. (See Errata Classification below).
Generally, errata are classified into several distinct types. The most common classification distinguishes security, bugfix, and enhancement errata (orcharhino uses these three categories). However, some distributions may use up to four categories, as well as a somewhat different terminology.
The following table serves to clarify these differences:
|Symbol||Red Hat / CentOS||Fedora||SUSE|
In addition to errata types, most distributions distinguish between different severity levels for security errata (levels 1 to 4 / low, moderate, high, and critical). High severity security errata are clearly of particular importance (though this may be dependent on your organizations particular needs). Errata generally come with a detailed description, that allow system administrators to evaluate whether they are of importance to a particular organization.
Viewing an Erratum¶
The erratum overview page (for a given erratum) can be accessed via the list of errata:
Content > Errata >> list of errata > Errata ID of an erratum
An erratum overview page lists details on the erratum and question, and has additional tabs for relevant content hosts and repositories:
- The Errata link (1) will take you back to the errata page.
- The erratum selection menu (2) will allow you to navigate to the erratum overview pages for other errata.
- Note that there are additional tabs (3) on the erratum overview page.
- The information contained on the Details tab (4) is fairly self explanatory (and well worth the read).
- Note that “Affected Packages” (4) lists those (versions of) packages that fix the problem described by the erratum. The erratum is “applicable to a host” if that host has older versions of any of these packages installed.
The Content Hosts tab of the erratum overview page (for some given erratum) will list any content hosts (see also: Content Hosts) that the erratum can be applied to:
- A drop down filter (1) exists to filter the list by lifecycle environment. (See also: Lifecycle Environments).
- The Apply to Hosts button (2) allows you to apply the erratum you are viewing to the selected content hosts. (See Applying Errata below).
The Repositories tab of the erratum overview page (for some given erratum) will list any repositories (see also Products) containing the erratum:
- Clicking on a repository (in the Name column (1)) will take you to the relevant repository page.
- clicking on the corresponding product (in the Product column (2)) will take you to the relevant product overview page.
There are several ways to apply errata. One convenient way to apply multiple errata to multiple content hosts is to use the relevant bulk action on the content hosts page. (See also: Content Hosts).
Alternatively, you can select any errata you want applied on the errata page and use the Apply Errata button:
Content > Errata >> Apply Errata
This button will take you to the apply errata page, which lists any and all hosts for which any of the selected errata are applicable:
- A common use case would be to apply the selected errata only to the hosts of a particular lifecycle environment, and there is a filter (1) to facilitate this.
- Select any hosts that should have errata applied using the checkboxes (2) in the list of content hosts.
- Click the Next button (3) once you are done.
This will generally take you to a confirmation page asking you to publish a new minor content view (see also Content Views) version (2.1 in the following example):
- Review the changes you are about to make (1).
- There is a checkbox to apply the errata immediately after publishing the new minor content view version.
- Select Confirm (2) to create the needed minor content view version.
A relevant task will appear:
- The More Details link (1) will take you to the task overview page for the task. (See also Tasks).
- Tasks of this type may take some time to complete.
Finally, it is also possible to apply individual errata via the relevant erratum overview page (see Viewing an Erratum above):
Content > Errata >> list of errata > Errata ID of an erratum > Content Hosts tab > Apply to Hosts
This button will ask you to confirm the creation of an incremental content view version (the process is near identical to the one above):
- Select the checkbox (1) to ensure the erratum is applied once the content view version has finished publishing.
- Select Confirm (2) to create the relevant task.