Bug 1750811
Summary: | Content View publish with dep solve and no filters adds recursive flag | ||
---|---|---|---|
Product: | Red Hat Satellite | Reporter: | Partha Aji <paji> |
Component: | Content Views | Assignee: | satellite6-bugs <satellite6-bugs> |
Status: | CLOSED ERRATA | QA Contact: | Lai <ltran> |
Severity: | medium | Docs Contact: | |
Priority: | unspecified | ||
Version: | 6.6.0 | CC: | pcreech |
Target Milestone: | 6.7.0 | Keywords: | 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: | 2020-04-14 13:25:37 UTC | 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: |
Description
Partha Aji
2019-09-10 14:02:55 UTC
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 |