Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
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:
Ignorable content setting in repo creation dialog does not actually ignore srpms. Also reproducible using hammer
Version-Release number of selected component (if applicable):
satellite-6.4.0-9.beta.el7sat.noarch
Additional info:
The problem is known https://github.com/Katello/katello/pull/7325, waiting on patch https://github.com/pulp/pulp_rpm/pull/1100 landing downstream. Filing this bug to make sure it happens, and also to skip the associated test in robottelo.
Hi Peter,
Thanks for raising this bugzilla. It looks like it may be a duplicate of bug 1335621; however, that bug was not correctly triaged to 6.4.
Mind if we close this one as a duplicate?
Peter, closing this as a duplicate based upon comment 2. Please re-open if there are any concerns. Thanks!
*** This bug has been marked as a duplicate of bug 1335621 ***