Bug 1426721

Summary:	[RFE] Alter the database status check to not rely on systemd
Product:	Red Hat CloudForms Management Engine	Reporter:	Nick Carboni <ncarboni>
Component:	Appliance	Assignee:	Gregg Tanzillo <gtanzill>
Status:	CLOSED DUPLICATE	QA Contact:	luke couzens <lcouzens>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	5.7.0	CC:	abellott, jhardy, lcouzens, obarenbo
Target Milestone:	GA	Keywords:	FutureFeature
Target Release:	cfme-future
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:	2017-03-06 22:00:35 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 Nick Carboni 2017-02-24 16:41:45 UTC

Description of problem:
Right now the console summary only lists the database as running if it is running under systemd.

In some cases (repmgr) the database is started using pg_ctl directly rather than systemctl. This will cause the console summary to report that the database is not running.

I propose that we use `pg_ctl -D $APPLIANCE_PG_DATA status` to determine the status of the database as that will always be correct.

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

Comment 2 Nick Carboni 2017-03-06 22:00:35 UTC


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