Uploaded image for project: 'Satellite'
  1. Satellite
  2. SAT-16260

Content view publish with filters is getting failed with error "Could not find the following content units:"

XMLWordPrintable

    • Sprint 113, Sprint 115, Sprint 116, Sprint 117, Sprint 118, Sprint 119, Sprint 120
    • Important
    • None

      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

              iballou@redhat.com Ian Ballou
              jira-bugzilla-migration RH Bugzilla Integration
              Cole Higgins Cole Higgins
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated:
                Resolved: