Bug 2222893
| Summary: | [Documentation Bug] - package dependencies can cause significant delays to Content View promotion | ||
|---|---|---|---|
| Product: | Red Hat Satellite | Reporter: | Dhaval Joshi <dhjoshi> |
| Component: | Content Views | Assignee: | Aneta Šteflová Petrová <apetrova> |
| Status: | CLOSED CURRENTRELEASE | QA Contact: | Satellite QE Team <sat-qe-bz-list> |
| Severity: | medium | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 6.13.2 | CC: | bangelic, iballou, sajha, saydas |
| Target Milestone: | Unspecified | Keywords: | Documentation, 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: | 2023-12-01 12:33:57 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
Dhaval Joshi
2023-07-14 11:30:06 UTC
To add on. It's not just the Dep-Solving that is a costly operation. But even without dep-solving enabled, a publish task with few exclude or include filters can prove to be costly Without any filters a CV publish would take about a min or three to complete. As soon as we add some ERRATA by date Exclude\INclude filter, That same task can take up to 20\30 mins to complete. If this is a known behavior, Then perhaps we should document this as well in the same section, just after the Dep-Solving part Hello, Many thanks for reporting this issue/suggestion for documentation improvement. Important pices of information about the progress of the doc fix will be shared in this ticket as well the link to the updated documents. Thank you! Just to summarize my initial investigation of the docs in question: Since this BZ was filed, 2 pull requests have been merged that change the documentation around dependency resolution significantly. * https://github.com/theforeman/foreman-documentation/pull/2240 * https://github.com/theforeman/foreman-documentation/pull/2300 These have been cherry-picked only down to version 3.5 (= 6.13 downstream). So while the problem most probably persists in versions 6.12 and previous, it might not be present in version 6.13 anymore. In 6.13, the following sections cover dependency resolution: * 7.8. Resolving Package Dependencies * 10.5. Limitations to Repository Dependency Resolution https://access.redhat.com/documentation/en-us/red_hat_satellite/6.13/html-single/managing_content/index#Resolving_Package_Dependencies_content-management Next steps: Find out if the problem still exists in 6.13. If not, find out if the older versions can be updated as well. If yes, fix it in all versions. (In reply to Dhaval Joshi from comment #0) > I suggest the below correction: > > "Note that resolving package dependencies can cause significant delays in > Content View publish tasks" With the latest doc version, section 7.7. Resolving Package Dependencies states the following: * "When incrementally adding a security errata to a Content View, dependency solving can cause significant delays to Content View publication without major benefits." * "Significant delay in Content View publication Satellite examines every repository in a Content View for dependencies. Therefore, publish time increases with more repositories." Based on this, I'd say the bug reported in c#0 has been fixed in the latest version (6.13). Ian, was there a specific reason why your PR that initiated the updates to dependency solving was submitted only for Satellite versions 6.13 and later? https://github.com/theforeman/foreman-documentation/pull/2240 If not, can I make the same updates to versions 6.12 and 6.11 as well? I believe sections 7.7. Resolving Package Dependencies, 7.8. Enabling Dependency Solving for a Content View, and 7.1. Creating a Content View[1] would be subject to the backport. [1] https://access.redhat.com/documentation/en-us/red_hat_satellite/6.13/html/managing_content/managing_content_views_content-management#Resolving_Package_Dependencies_content-management Aneta, there was no specific reason, we can backport it to any version of the Satellite docs. PR to backport the latest version of dependency solving docs into Satellite versions 6.12 and 6.11: https://github.com/theforeman/foreman-documentation/pull/2505 This doesn't resolve the issue reported in c#1. I will look into that once the backporting is taken care of. (In reply to Aneta Šteflová Petrová from comment #7) > PR to backport the latest version of dependency solving docs into Satellite > versions 6.12 and 6.11: > https://github.com/theforeman/foreman-documentation/pull/2505 PR merged: https://github.com/theforeman/foreman-documentation/pull/2505#issuecomment-1776609940 The next step is now to investigate what else needs to be updated to fully resolve this issue. PR to address the remaining part of this BZ: https://github.com/theforeman/foreman-documentation/pull/2603 |