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.
DescriptionJustin Sherrill
2016-03-22 15:26:01 UTC
Description of problem:
"Errata by id" exclude filter does not seem to be working properly
Version-Release number of selected component (if applicable):
6.2 snap4
How reproducible:
always
Steps to Reproduce:
1. Create and sync a repo (such as https://jlsherrill.fedorapeople.org/fake-repos/needed-errata/)
2. Add the repo to a content view
3. Add an errata by id exclude filter and select the 'sea erratum'
4. Publish the content view
Actual results:
Generated version still includes the excluded erratum and packages
Expected results:
Errata and none of its packages are in the published version
Additional info:
Comment 2pulp-infra@redhat.com
2016-03-23 18:00:52 UTC
The Pulp upstream bug status is at ASSIGNED. Updating the external tracker on this bug.
Comment 3pulp-infra@redhat.com
2016-03-23 18:00:54 UTC
The Pulp upstream bug priority is at High. Updating the external tracker on this bug.
Comment 4pulp-infra@redhat.com
2016-03-28 20:33:36 UTC
The Pulp upstream bug status is at POST. Updating the external tracker on this bug.
Comment 6pulp-infra@redhat.com
2016-04-06 13:33:39 UTC
The Pulp upstream bug status is at MODIFIED. Updating the external tracker on this bug.
This downstream merge causes this error upon syncing content:
pulp.server.webservices.middleware.exception:ERROR: (10716-95680) File "/usr/lib64/python2.7/site-packages/bson/objectid.py", line 52, in _raise_invalid_id
pulp.server.webservices.middleware.exception:ERROR: (10716-95680) " or a 24-character hex string" %% oid)
pulp.server.webservices.middleware.exception:ERROR: (10716-95680) InvalidId: '016ba778-1665-4ef7-bc0a-adf99472d6f5' is not a valid ObjectId, it must be a 12-byte input or a 24-character hex string
celery.worker.strategy:INFO: Received task: pulp.server.async.tasks._queue_reserved_task[af6c1d5f-0ebc-4c19-8e2b-c49f4244b0a6]
failing it
VERIFIED.
@Sat6.2.0-Beta-Snap8.2
pulp-*-2.8.1.3-1.el7sat.noarch
used manual reproducer described in comment #0 and I got these CV versions:
Version 1.0
32 Packages
4 Errata ( 3 0 1 )
Version 2.0 <- sea erratum excluded by id
29 Packages
3 Errata ( 2 0 1 )
Packages/Errata tab counts match with Summary above
Comment 9pulp-infra@redhat.com
2016-04-26 23:04:16 UTC
The Pulp upstream bug status is at ON_QA. Updating the external tracker on this bug.
Comment 10pulp-infra@redhat.com
2016-05-06 17:21:03 UTC
The Pulp upstream bug status is at VERIFIED. Updating the external tracker on this bug.
Comment 11pulp-infra@redhat.com
2016-05-17 20:01:14 UTC
The Pulp upstream bug status is at CLOSED - CURRENTRELEASE. Updating the external tracker on this bug.
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.
https://access.redhat.com/errata/RHBA-2016:1501