Bug 1357839

Summary:	[RFE] Installer should check the status of free space in root (/) and throw a warning in case it is lacking
Product:	Red Hat Satellite	Reporter:	Nenad Peric <nperic>
Component:	Installation	Assignee:	Chris Roberts <chrobert>
Status:	CLOSED DUPLICATE	QA Contact:
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	6.2.0	CC:	bbuckingham, chrobert, stbenjam
Target Milestone:	Unspecified	Keywords:	FutureFeature, 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:	2016-08-23 16:53:50 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 Nenad Peric 2016-07-19 11:02:18 UTC

Description of problem:

If there is not enough space to sync things and work with Satellite after it has been installed, (namely / fs) a lot of funny things can happen which are not immediately obvious. 
Unknown errors (Something went wrong) and mongo connection issues can pop up which in turn would cause a lot of issues with Satellite itself. 

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


How reproducible:

Every time you run out of space in /

Steps to Reproduce:

Get the / FS to 100%, stuff just starts breaking but the errors Sat is giving out do not help in determining the real issue. 


Expected results:

Perhaps a feature should be added to the installer which warns the user if the remaining space in / fs is too low for syncing a few ISOs afterwards (say less than 20GB remaining?). 
It should not be a critical error, since the user could potentially allocate more space to / after the installation is complete. 
The default RHEL 7 installation allocates inadequate amount of space to the / fs for Satellite usage (around 50GB in my default setup).

Comment 2 Stephen Benjamin 2016-08-23 16:53:50 UTC


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