Composite View with rpm package filter

Latest response

Hi everyone,

I am trying to exclude ansible from EPEL in a content view. This is simple and straightforward. Publish a new version and the package is gone.

However, when I include the EPEL version with filter in a composite content view, the ansible packages are still found.

In the composite view, I make sure the proper version of EPEL is selected (but latest should be fine too, I tried both ways) and I publish a new version of the composite view. I then promote it to the correct lifecycle environment.

When I give a client direct access to the regular content view with the filter it works and a yum search ansible --showduplicates doesn't show the filtered versions of ansible from EPEL. when I use the composite view the filter doesn't work and yum search finds the versions from EPEL.

Any ideas what I could be doing wrong?

Thanks!

Responses