Content Lifecycle deny filter not excluding package

This document (000021007) is provided subject to the disclaimer at the end of this document.

Environment

SUSE Manager Server 4.3

Situation

After configuring a NEVRA (Name, Epoch, Version, Release, Architecture) package filter to exclude a specific package version and rebuilding the project, the package is not excluded. The following error is logged in the "/var/log/rhn/rhn_web_frontend.log", excerpt:

... - <configured_filter_name> NEVRA: We couldn't find a matching filter for nevr

Resolution

The NEVRA options need to be properly specified, the name can not include anything other than the exact package name and the version and release information need to be accurately included.

Cause

The NEVRA options are not properly specified and does not match the to be excluded packages NEVRA attributes.

Additional Information

To see the NEVRA attributes for a specific RPM, the following command can be used on a system already having the package installed, for example taking the package "xen-libs":

rpm --queryformat "%{NAME} %{EPOCH} %{VERSION} %{RELEASE} %{ARCH}" -q xen-libs
xen-libs (none) 4.14.5_08 150300.3.40.1 x86_64

Using the above information, a proper NEVRA filter can then be:

Package Name: xen-libs
Version: 4*
Release: 150400*
Architecture: x86_64

An example of an incorrect filter that will result in the package not being excluded:

Package Name: xen-libs-4
Version: 0.0
Release: 1
Architecture: x86_64

Disclaimer

This Support Knowledgebase provides a valuable tool for SUSE customers and parties interested in our products and solutions to acquire information, ideas and learn from one another. Materials are provided for informational, personal or non-commercial use within your organization and are presented "AS IS" WITHOUT WARRANTY OF ANY KIND.