Bug 1293750

Summary:	[RFE] Satellite 5.7: help customer detect db space before upgrade and how to expand
Product:	Red Hat Satellite 5	Reporter:	Xixi <xdmoon>
Component:	Upgrades	Assignee:	Tomáš Kašpárek <tkasparek>
Status:	CLOSED DEFERRED	QA Contact:	Red Hat Satellite QA List <satqe-list>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	570	CC:	dyordano, mmello, shughes, tlestach
Target Milestone:	---	Keywords:	FutureFeature, UserExperience
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Enhancement
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2018-04-09 14:53:51 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:
Bug Depends On:
Bug Blocks:	260381

Description Xixi 2015-12-23 00:44:43 UTC

Description of problem:
Customer running out of disk space for db during upgrade: may need assistance in extending LVM volume etc. Can upgrade/installer detect this and help point customers to RHEL docs on managing disk space?

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


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 1 Tomáš Kašpárek 2016-01-05 13:03:59 UTC

There are two major concerns about this: detecting whether the DB is embedded or external one, how to behave when the DB is external one.
Second one: determining LVM status and free space on LVM which contains /var/lib/pgsql, what if LVM is not used?
This would increase effort spent on this one, also Satellite is not here to monitor LVM partitions and to teach users how to expand them.

Comment 2 Tomas Lestach 2018-04-09 14:53:51 UTC

We have re-reviewed this bug, as part of an ongoing effort to improve Satellite/Proxy feature and bug updates, review and backlog.

This is a low priority bug and has no currently open customer cases. While this bug may still valid, we do not see it being implemented prior to the EOL of the Satellite 5.x product. As such, this is being CLOSED DEFERRED. 

Closing now to help set customer expectations as early as possible. You are welcome to re-open this bug if needed.