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.

Bug 2151474

Summary: On Demand download policy does not scale for LEAPP upgrades or convert2RHEL
Product: Red Hat Satellite Reporter: Pavel Moravec <pmoravec>
Component: PulpAssignee: satellite6-bugs <satellite6-bugs>
Status: CLOSED MIGRATED QA Contact: Satellite QE Team <sat-qe-bz-list>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 6.12.0CC: dalley, dkliban, ggainey, rchan
Target Milestone: UnspecifiedKeywords: MigratedToJIRA, 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: 2024-06-06 12:55:54 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 Pavel Moravec 2022-12-07 09:51:34 UTC 
Description of problem:
During a LEAPP upgrade of a Satellite client, or during its convert2RHEL procedure, the client can easily hit timeout errors when downloading packages from Satellite.

This happens when the repositories with the packages have On Demand download policy (which is the default) and when majority of the packages are not yet downloaded. The feature is not tuned or scaled up for a bulk request of hundreds or even thousands of packages to download from Satellite.

This ends up in repeated upgrade (or convert) failures, always on timeouts of different packages download.

I dont know if this is a known limitation of On Demand policy or a scalability bug. If the later, please fix it. If the first, please reassign the bug to Documentation, to mention in:

https://access.redhat.com/documentation/en-us/red_hat_satellite/6.12/html-single/managing_hosts/index#Upgrading_Hosts_From_RHEL7_to_RHEL8_managing-hosts

and

https://access.redhat.com/documentation/en-us/red_hat_satellite/6.12/html-single/managing_hosts/index#converting-a-host-to-rhel_managing-hosts

that all the repositories the client will fetch packages from are *recommended* to have Immediate download policy and the repositories should have been synced with that policy, already.

See https://access.redhat.com/solutions/6989411 for a reference of underlying customer problem.


Version-Release number of selected component (if applicable):
Sat 6 (any version incl. 6.12)


How reproducible:
100%


Steps to Reproduce:
1. Sync RHEL8 repos (with the default On Deamnd download policy) to a Satellite
2. Have a RHEL7 client system and run LEAPP upgrade on it
3. Optionally, convert a CentOS / Oracle Linux system to RHEL


Actual results:
2. or 3. is supposed to fail with errors like in https://access.redhat.com/solutions/6989411


Expected results:
Either add to our documentation the recommendation "use immediate download policy", or make the On Demand more scalable.


Additional info:
Comment 1 Daniel Alley 2023-12-04 16:44:26 UTC 
Potentially resolved by https://github.com/pulp/pulpcore/pull/4836

We can test it by adding an index to this table manually on a test system which is exhibiting this behavior.
Comment 2 Pavel Moravec 2023-12-04 18:22:40 UTC 
(In reply to Daniel Alley from comment #1)
> Potentially resolved by https://github.com/pulp/pulpcore/pull/4836
> 
> We can test it by adding an index to this table manually on a test system
> which is exhibiting this behavior.

Tat can definitely speed up the stuff, but I thought the main bottleneck is the limited concurrency of syncing packages from CDN to Satellite during bulk request of RPMs from a client..?
Comment 3 Daniel Alley 2023-12-04 21:42:00 UTC 
It could be, it's a bit hard to say.  If that's the case it can *probably* be addressed by increasing the number of content workers?
Comment 4 Pavel Moravec 2023-12-04 21:49:39 UTC 
(In reply to Daniel Alley from comment #3)
> It could be, it's a bit hard to say.  If that's the case it can *probably*
> be addressed by increasing the number of content workers?

Yes, I think so.
Comment 5 Eric Helms 2024-06-06 12:55:54 UTC 
This BZ has been automatically migrated to the issues.redhat.com Red Hat Issue Tracker. All future work related to this report will be managed there.

Due to differences in account names between systems, some fields were not replicated.  Be sure to add yourself to Jira issue's "Watchers" field to continue receiving updates and add others to the "Need Info From" field to continue requesting information.

To find the migrated issue, look in the "Links" section for a direct link to the new issue location. The issue key will have an icon of 2 footprints next to it, and begin with "SAT-" followed by an integer.  You can also find this issue by visiting https://issues.redhat.com/issues/?jql= and searching the "Bugzilla Bug" field for this BZ's number, e.g. a search like:

"Bugzilla Bug" = 1234567

In the event you have trouble locating or viewing this issue, you can file an issue by sending mail to rh-issues. You can also visit https://access.redhat.com/articles/7032570 for general account information.