Bug 2172355
| Summary: | Content view publish with filters is getting failed with error "Could not find the following content units:" | ||
|---|---|---|---|
| Product: | Red Hat Satellite | Reporter: | dprabhu |
| Component: | Content Views | Assignee: | Ian Ballou <iballou> |
| Status: | VERIFIED --- | QA Contact: | Cole Higgins <chiggins> |
| Severity: | high | Docs Contact: | |
| Priority: | high | ||
| Version: | 6.12.1 | CC: | ahumbe, chiggins, dalley, iballou, pcreech, sajha, snarya |
| Target Milestone: | 6.14.0 | Keywords: | PrioBumpGSS, Triaged |
| Target Release: | Unused | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | Type: | Bug | |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
Created redmine issue https://projects.theforeman.org/issues/36334 from this bug Upstream bug assigned to iballou Upstream bug assigned to iballou 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. Moving this bug to POST for triage into Satellite since the upstream issue https://projects.theforeman.org/issues/36334 has been resolved. |
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