Bug 2172355 - Content view publish with filters is getting failed with error "Could not find the following content units:"
Summary: Content view publish with filters is getting failed with error "Could not fin...
Keywords:
Status: VERIFIED
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Content Views
Version: 6.12.1
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: 6.14.0
Assignee: Ian Ballou
QA Contact: Cole Higgins
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2023-02-22 05:15 UTC by dprabhu
Modified: 2023-07-25 21:13 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed:
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Foreman Issue Tracker 36334 0 High Closed Content view publish with filters is getting failed with error "Could not find the following content units:" 2023-05-31 17:30:30 UTC
Red Hat Issue Tracker SAT-16260 0 None None None 2023-03-02 15:38:11 UTC

Description dprabhu 2023-02-22 05:15:36 UTC
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

Comment 9 Ian Ballou 2023-04-26 19:34:00 UTC
Created redmine issue https://projects.theforeman.org/issues/36334 from this bug

Comment 10 Bryan Kearney 2023-05-03 00:03:19 UTC
Upstream bug assigned to iballou

Comment 11 Bryan Kearney 2023-05-03 00:03:22 UTC
Upstream bug assigned to iballou

Comment 12 Ian Ballou 2023-05-17 19:31:36 UTC
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.

Comment 13 Bryan Kearney 2023-05-31 16:02:56 UTC
Moving this bug to POST for triage into Satellite since the upstream issue https://projects.theforeman.org/issues/36334 has been resolved.


Note You need to log in before you can comment on or make changes to this bug.