Bug 1304790

Summary:	[RFE] Notify the admin via email or show notification in UI when Satellite host runs below the recommended free space
Product:	Red Hat Satellite	Reporter:	sthirugn <sthirugn>
Component:	Performance	Assignee:	satellite6-bugs <satellite6-bugs>
Status:	CLOSED DUPLICATE	QA Contact:
Severity:	medium	Docs Contact:
Priority:	medium
Version:	6.1.6	CC:	bbuckingham, bkearney, dcaplan, inecas, sshtein
Target Milestone:	Unspecified	Keywords:	FutureFeature, UserExperience
Target Release:	Unused
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Enhancement
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2018-07-18 17:41:28 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 sthirugn@redhat.com 2016-02-04 15:52:34 UTC

Description of problem:
[RFE] Notify the admin when Satellite host runs below the recommended free space

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

How reproducible:


Steps to Reproduce:
Some customers experience very slow publish process due to lack of free space.

Actual results:


Expected results:
The admin should be noticed via email or notification in UI if Satellite6 host runs out of recommended free space.

Additional info:

Comment 1 David Caplan 2016-02-04 16:01:15 UTC

I would add to the Actual results the need for Satellite 6 to shutdown gracefully when it's available storage drops to within some percentage of its required storage. This percentage should be tunable without the need for a patch or Z-Stream.

When the threshold is crossed, notifications are sent through the logging system, the email notification system, and through the UI (e.g. wall message indicating that the Satellite Server is shutting down). 

Graceful shutdown is far easier to recover from than the current circumstance where things start to collapse and the DB has the potential for corruption (as is being observed at multiple customers.

Comment 9 Bryan Kearney 2018-07-18 17:41:28 UTC


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