Bug 1694836

Summary: [RFE] Satellite should report size of repository before selecting it to sync.
Product: Red Hat Satellite Reporter: Skip Wyatt <awyatt>
Component: PulpAssignee: satellite6-bugs <satellite6-bugs>
Status: CLOSED DUPLICATE QA Contact: Lai <ltran>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 6.4.2CC: bkearney, dalley, mvanderw, rjerrido, satellite6-bugs, ttereshc
Target Milestone: UnspecifiedKeywords: FutureFeature, Triaged
Target Release: Unused   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2022-08-25 00:34:49 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 Skip Wyatt 2019-04-01 19:59:20 UTC
Description of problem:
Customers select repositories to sync and then run the Satellite out of disk space during the sync because the Repos to not show the approximate size when enabling them

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

How reproducible:
Always


Additional info:
The requested functionality is to show an approximate repository size in the Red Hat Repositories screen, so that customers can see the approximate size of the repo before they hit the sync button and then realize they have to expand their disk or LV.

We realize that there is rule of thumb guidelines for disk space in the documentation, but if it could be added to the metadata for the repos to be synced that would help.

Comment 9 Tanya Tereshchenko 2021-06-04 19:30:06 UTC
This RFE is not on the roadmap in the short term, we will re-evaluate it in a few months.

Comment 10 Tanya Tereshchenko 2021-10-30 15:17:54 UTC
This RFE is not on the roadmap in the short term, we will re-evaluate it in a few months.

Comment 13 Daniel Alley 2022-08-25 00:34:49 UTC
Closing as duplicate of https://bugzilla.redhat.com/show_bug.cgi?id=1940951

*** This bug has been marked as a duplicate of bug 1940951 ***