Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
Red Hat Satellite engineering is moving the tracking of its product development work on Satellite to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "Satellite project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs will be migrated starting at the end of May. If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "Satellite project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/SAT-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Description of problem:
When publishing a content view with dep solve turned on, satellite now includes additional repositories in the same content view. While this works well it doubles typical depsolve publish time.
Version-Release number of selected component (if applicable): 6.7 and above
Steps to Reproduce:
1. Create a content view with a bunch of RHEL repositories
2. Add a module includes filter
3. Turn depsolve on the content view
4. Check on the publish time
Actual results:
In my environment with AppStream and BaseOS
- No Depsolve - 11s
- Dep Solve without additional repos (look at single repo only.): 90s
- Dep Solve with "additional-repositories" : 204s
Wondering whether we need a setting or option to turn off multi-repo lookup.
The issue here is not the depsolving itself, but the preparation needed to be able to do the depsolving. Specificially, metadata about every single RPM, module, etc. in every repository considered by the depsolving must be fetched from the database and loaded into the depsolver. The amount of querying and IO this requires makes it fundamentally somewhat slow, and we're already bypassing mongoengine and making raw Mongo queries to reduce overhead and increase speed, so I'm not sure what more we can do without introducing caching which would be very difficult to get correct (cache invalidation issues, etc.)
Upon review of our valid but aging backlog the Satellite Team has concluded that this Bugzilla does not meet the criteria for a resolution in the near term, and are planning to close in a month. This message may be a repeat of a previous update and the bug is again being considered to be closed. If you have any concerns about this, please contact your Red Hat Account team. Thank you.
Thank you for your interest in Red Hat Satellite. We have evaluated this request, and while we recognize that it is a valid request, we do not expect this to be implemented in the product in the foreseeable future. This is due to other priorities for the product, and not a reflection on the request itself. We are therefore closing this out as WONTFIX. If you have any concerns about this feel free to contact your Red Hat Account Team. Thank you.