Description of problem: During a content view publish, satellite directs pulp to copy contents between 2 repos. Now if the "solve dependencies" is set on the content view, satellite automatically sets "recursive_conservative: true" when that copy operation is executed. This recursive_conservative flag is set even if no filters were specified on the content view. Meaning it could potentially end up dep solving in all rpms in a repo instead of just a subset. This could unnecessarily slow down the publish times (since depsolve takes a much longer time). Version-Release number of selected component (if applicable): 6.6 beta How reproducible: Steps to Reproduce: 1. Have a content view with solve dependencies set to true and no filters 2. Add a large repo to the cv (like rhel 8) 3. Publish Actual results: Publish that takes much longer even though there are no filters. Expected results: Publish that takes about the same time as publish without dep solving
Created redmine issue https://projects.theforeman.org/issues/28039 from this bug
Moving this bug to POST for triage into Satellite 6 since the upstream issue https://projects.theforeman.org/issues/28039 has been resolved.
Steps to Test: 1. Have a content view with solve dependencies set to true and no filters 2. Add a large repo to the cv (like rhel 8) 3. Publish Actual results: Publish takes about 4 to 5 minutes to complete. Expected results: Publish takes about 4 to 5 minutes to complete. Note: I've tested using repos that had 10k to 70k packages. 10k took about 5 minutes to publish while anything beyond 20k took about 15 minutes with and without depsolving. It does show even though depsolving is turned on without filters, it doesn't depsolve to keep the publish time consistent with turning depsolving off. Both true and false flag retains consistent publish time. Tested on 6.7.0_09. Marking issue as verified.
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/RHSA-2020:1454