The errata page can be accessed via the content menu:

Content > Errata

The errata page forms a part of orcharhino’s content management.

Errata are one content type supported by orcharhino. Content of type errata is contained in repositories of type yum or deb.

Errata describe fixes (patches) for packages with known issues. Currently orcharhino supports errata for packages of type RPM as well as deb. The errata system may also be used to perform critical security updates on software that cannot be updated to its 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).

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

Email notifications may help you keeping track of available errata for specific hosts. Navigate to the users page to enable email notifications.

The ATIX Debian and Ubuntu Errata service provides errata for Debian and Ubuntu. When creating a repository of type deb, point the Errata URL at ATIX’s Debian and Ubuntu Errata Parser server. Use for Debian and for Ubuntu.

An erratum contains the information which packages have to be updated to fix a security issue. Debian and Ubuntu errata are derived from the Debian security announcements (DSA) and the Ubuntu security notices (USN).

Ensure to only add Debian and Ubuntu errata to Debian and Ubuntu repositories that contain the packages needed to apply the errata. For Debian, you need the <debian_release>/updates repository, for example bullseye/updates. For Ubuntu, you need the <ubuntu_release>-security repository, for example focal-security.

The errata page includes several filter options, an Apply Errata button, and a list of available errata:

List of 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 checkbox (2) will filter the list of errata (5) to show only those errata, that are applicable to one or more content hosts.

  • The Installable checkbox (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.

  • Clicking on an erratum in the Errata ID column (6) will take you to the erratum overview page for that erratum.

  • The Type column (7) is of particular importance to the evaluation of available errata.

Errata Classification

In general, errata are classified into several distinct types. The most common classification distinguishes security, bugfix, and enhancement errata, which is used by orcharhino. 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 CentOS/Oracle Linux/RHEL SLES Debian/Ubuntu












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 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 in question and has additional tabs for relevant content hosts and repositories:

Details of an erratum
  • 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 will list any content host that the erratum can be applied to:

List of content hosts affected by a specific erratum

The Repositories tab of the erratum overview page will list any repositories containing the erratum:

List of repositories containing a specific 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.

Applying Errata

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.

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:

Applying errata
  • 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 you want to apply errata on 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 version (2.1 in the following example):

Confirm to apply errata
  • 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 task which applies the errata to one or more content hosts
  • The More Details link (1) will take you to the task overview page.

  • Tasks of this type may take some time to complete.

It is also possible to apply individual errata via the relevant erratum overview page:

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):

Confirm to create a incremental content view in order to apply errata
  • 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.