Red Hat Satellite engineering is moving the tracking of its product development work on Satellite to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "Satellite project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs will be migrated starting at the end of May. If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "Satellite project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/SAT-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Description of problem:

When using a filter like nagios-plugins-* with the on-demand download policy the packages aren't available.


Version-Release number of selected component (if applicable):

6.2.6


Steps to Reproduce:

1. Add a filter with a wildcard to on-demand repo.
2. Publish and promote CV.
3. Try to install package on a host.


Actual results:

Unable to install package, yum fails with error.


Expected results:

To be able to install the packages that fall under the scope of the filter.


Additional info:

Packages with full names in the filters for that repo worked fine. The same filter in a repo with immediate policy works too.

I cannot seem to reproduce this issue and there isn't much information here.  

1) What error are you seeing on the yum side?
2) do the packages show up as being in that content view version in the UI?

Since its been a week, I'm going ahead and closing this.  In your situation i wonder if on_demand was working at all?  

If you are still able to produce, feel free to reopen.
Thanks