Troubleshooting missing patches in Red Hat patch catalogs

A Red Hat Linux Patch Catalog does not display the expected packages.

This topic helps you to locate and review the appropriate logs to determine why the expected packages are not being added to the Patch Catalog and either help you to identify and resolve the issue or create a BMC Customer Support case with the appropriate logs.

Issue symptoms

A Red Hat Linux Patch Catalog Update Job (CUJ) runs successfully without errors, however, some of the expected packages are missing from the catalog.

Issue scope

The issue might occur with all the RedHat Linux Patch CUJs in your environment or a specific CUJ.

Diagnosing and reporting an issue

Task	Action	Steps	Reference
1	Understand the problem scope.	Do the following: Identify the packages that are missing from the updated catalog Identify the affected versions of RedHat where this issue occurs. Check the defined filters list and whether it contains child channels. See the images in the Reference column.	Red Hat patch catalog: Filter list:
2	Identify the recent changes	Verify whether the same package was already present in the RedHat patch catalog. If yes, check whether any changes were made to the filters defined on the patch catalog.
3	Confirm whether the package is really missing by creating a Depot Smart Group	Do the following: Right-click the Redhat Patch Catalog and select New > Patch Catalog Smart Group. Provide a name for the Patch Catalog Smart Group. For example, LocatePackage is the name used in the example Smart Group in the Reference column. Add a condition to determine whether the package exists. For instance, “Any Depot Object Where ??NAME?? contains satellite” Click Finish. Expand the new Patch Catalog Smart Group to confirm whether the Package is missing as reported.	Filter not showing missing Package reported
4	Obtain the complete details of the missing package from the Red Hat Portal.	Do the following: Login to the Red Hat Portal with your Red Hat credentials. Enter the missing package name. Under the Architectures column, click the link corresponding to the package name to get the complete details (This is the NOARCH link in the example image, but that label may vary.) Note down the product (Variant, version, and architecture) and the Repo label. In the example image, it is "Red Hat Satellite 6.7 x86_64" Note the Repo Label value that corresponds to the channel.
5	Analysis	Review the information in the "Resolutions for common issues" section to understand the common issues that can result in packages being unexpectedly missing from a Red Hat catalog along with how they can typically be resolved. If you are unable to identify and resolve the problem, create a BMC Support Case.
6	Creating a BMC Support Case	Provide the following information and log files when creating a case with BMC Customer Support: Full problem scope as identified in step 1 Recent changes as identified in step 2 Log for the latest Patch Catalog Update Job (CUJ) run

Resolutions for common issues

Symptom	Action	Reference
Package is missing from one catalog, but is present in another catalog.	Do the following: Compare the filters defined for both the catalogs. Determine the filter on the successful CUJ that is responsible for downloading the missing package, and add the same filter to the problematic catalog. Rerun the problematic CUJ and confirm whether the package is included in the catalog.
The package was previously appearing in a patch catalog, but is no longer appearing after the recent CUJ runs.	Do the following: Check whether any filters were removed from the catalog recently. If yes, review the filter changes and whether any of these filters were responsible for downloading this missing package. If yes, consider adding the filter back. Rerun the problematic CUJ and confirm the package is now included in the Catalog as expected. If filters have not been removed recently, confirm whether the patch is still available for download directly from the vendor.
The Package is determined (step 4) to have a channel, OS version or architecture that is not included in the existing top-level catalog filter(s).	Do the following: Add the required filter to the catalog filter list. Rerun the CUJ. Confirm that the missing package is now present.	Walkthrough-Setting-up-and-managing-an-online-patch-catalog-for-Linux
The Package is determined (step 4) to belong to a child channel (see the Repo label) that is not defined on the patch catalog.	Do the following: Open the Patch catalog and add the required child channel to the appropriate filter. Rerun the CUJ. Confirm the missing package is now present.	Creating a RedHat patch catalog
The package is determined (step 4) to belong to a child channel (see the Repo label), which is not available for selection in the child channel list.	Follow the instructions in the referenced knowledge article to add the required channel to the list of channels available for selection in the selected child channel list.	KA 000359635
The Patch Analysis phase does not show some patches as missing, but in the commit phase same patches are reported as the following warning: <PATCH NAME> available, but not installed	The dnf utility checks whether the latest packages are available for installation. If you want, update the packages.