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:
While publishing the content view with filters applied it is getting failed with below error:
Errors:
Error message: the server returns an error
HTTP status code: 400
Response headers: {"Date"=>"Fri, 17 Feb 2023 14:40:33 GMT", "Server"=>"gunicorn", "Content-Type"=>"application/json", "Vary"=>"Accept,Cookie", "Allow"=>"POST, OPTIONS", "X-Frame-Options"=>"DENY", "Content-Length"=>"124", "X-Content-Type-Options"=>"nosniff", "Referrer-Policy"=>"same-origin", "Correlation-ID"=>"6e4c61c8-8845-4910-a77d-44992324651d", "Access-Control-Expose-Headers"=>"Correlation-ID", "Via"=>"1.1 mbgrhsat00001.iex.exch.int", "Connection"=>"close"}
Response body: ["Could not find the following content units: ['/pulp/api/v3/content/rpm/modulemds/08018868-b067-4907-b24e-ec5571b0d0b2/']"]
But content view publish successfully if filters are not applied to it.
Version-Release number of selected component (if applicable):
Satellite 6.12
How reproducible:
Steps to Reproduce:
1.
2.
3.
Actual results:
Content view publish with filters get fails with the below error:
Response body: ["Could not find the following content units: ['/pulp/api/v3/content/rpm/modulemds/08018868-b067-4907-b24e-ec5571b0d0b2/']"]
Expected results:
Content view publish with filters should complete successfully.
Additional info:
Same issue observed in upstream https://community.theforeman.org/t/strange-pulp3-error/25550
The likely workaround for this issue is to destroy all of the "by ID" filter rules on the content view and recreate them. One trigger for this bug is having filter rules for content that doesn't exist.
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 (Important: Satellite 6.14 security and bug fix update), 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/RHSA-2023:6818
Description of problem: While publishing the content view with filters applied it is getting failed with below error: Errors: Error message: the server returns an error HTTP status code: 400 Response headers: {"Date"=>"Fri, 17 Feb 2023 14:40:33 GMT", "Server"=>"gunicorn", "Content-Type"=>"application/json", "Vary"=>"Accept,Cookie", "Allow"=>"POST, OPTIONS", "X-Frame-Options"=>"DENY", "Content-Length"=>"124", "X-Content-Type-Options"=>"nosniff", "Referrer-Policy"=>"same-origin", "Correlation-ID"=>"6e4c61c8-8845-4910-a77d-44992324651d", "Access-Control-Expose-Headers"=>"Correlation-ID", "Via"=>"1.1 mbgrhsat00001.iex.exch.int", "Connection"=>"close"} Response body: ["Could not find the following content units: ['/pulp/api/v3/content/rpm/modulemds/08018868-b067-4907-b24e-ec5571b0d0b2/']"] But content view publish successfully if filters are not applied to it. Version-Release number of selected component (if applicable): Satellite 6.12 How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Content view publish with filters get fails with the below error: Response body: ["Could not find the following content units: ['/pulp/api/v3/content/rpm/modulemds/08018868-b067-4907-b24e-ec5571b0d0b2/']"] Expected results: Content view publish with filters should complete successfully. Additional info: Same issue observed in upstream https://community.theforeman.org/t/strange-pulp3-error/25550