Bug 2219885 - Satellite using the feature 'Alternate Content Source' is getting errors
Summary: Satellite using the feature 'Alternate Content Source' is getting errors
Keywords:
Status: ASSIGNED
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Pulp
Version: 6.13.1
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: Unspecified
Assignee: satellite6-bugs
QA Contact: Satellite QE Team
URL:
Whiteboard:
: 2223165 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2023-07-05 17:03 UTC by Aldrey Souza
Modified: 2023-08-17 09:14 UTC (History)
8 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed:
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker SAT-18815 0 None None None 2023-07-06 14:05:54 UTC

Description Aldrey Souza 2023-07-05 17:03:38 UTC
Description of problem:
 Configuring the feature 'Alternate Content Source' (ACS) to use the Capsule gets 'Out of memory' errors.

Version-Release number of selected component (if applicable):
 Satellite 6.13.1

How reproducible:
 Create an ACS to sync the product 'Red Hat Enterprise Linux for x86_64'

Steps to Reproduce:
 1. Satellite WebUI
 2. Content
 3. Alternate Content Sources
 4. Click over the button 'Add Source'
 5. Select the option 'Simplified' -> Next
 6. Type: 
     Name: RHEL 8 and 9
     Description: RHEL 8 and 9
     -> Next
 7. Select one capsule -> Next
 8. Select the products: Red Hat Enterprise Linux for x86_64 -> Next 
 9. Click over the button 'Add'
 10. Click over the button 'Refresh source'

Actual results:
 The server is not able to refresh the ACS, getting the 'Out of memory' errors

Expected results:
 The server is able to refresh the ACS using the current resources without errors

Additional info:

Comment 7 Ian Ballou 2023-07-26 16:11:37 UTC
*** Bug 2223165 has been marked as a duplicate of this bug. ***


Note You need to log in before you can comment on or make changes to this bug.