Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 977828

Summary:	db-control: start is not synchronous
Product:	Red Hat Satellite 5	Reporter:	Matej Kollar <mkollar>
Component:	Server	Assignee:	Tomáš Kašpárek <tkasparek>
Status:	CLOSED CANTFIX	QA Contact:	Red Hat Satellite QA List <satqe-list>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	unspecified	CC:	tkasparek, tlestach
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2016-03-31 14:33:52 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:
Bug Depends On:
Bug Blocks:	462714

Description Matej Kollar 2013-06-25 12:39:06 UTC

Description of problem:

  Running "db-control start" seems like not synchronous.
  Querying state with "db-control status" can indicate that database
  is down if run immediately after start.

Version-Release number of selected component:

  spacewalk-dobby-1.9.22-15

How reproducible:

  not easy

Steps to Reproduce:

  0. prepare database that is used "a little".
  1. db-control stop
  2. db-control start
  3. db-control status

Actual results:
  # db-control status
  The database is offline.

Expected results:
  # db-control status
  The database is running and accepting connections.

Comment 4 Tomas Lestach 2013-08-14 12:15:05 UTC

A similar issue was addressed within Bug 972626.

Comment 6 Tomas Lestach 2016-03-31 14:33:52 UTC

Based on Comment 3 this is not a Satellite 5 issue, rather a postgresql service issue. Closing as CANTFIX.