Bug 663315

Summary: 'db-control stop' only starts database shutdown process
Product: Red Hat Satellite 5 Reporter: Jiri Kastner <jkastner>
Component: ServerAssignee: Miroslav Suchý <msuchy>
Status: CLOSED CURRENTRELEASE QA Contact: Martin Minar <mminar>
Severity: medium Docs Contact:
Priority: low    
Version: unspecifiedCC: cperry, mkoci, mkollar, mminar, msuchy
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: spacewalk-web-1.7.28-2 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-10-01 21:58:55 UTC Type: ---
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: 819032    

Description Jiri Kastner 2010-12-15 11:07:05 UTC 
Description of problem:
'db-control stop' according to documentation should stop rhn database instance, but instead of this, it only starts shutdown process.

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


How reproducible:


Steps to Reproduce:
1. db-control stop && db-control status
2. check output (db in shutdown process)
3. sleep 10s && db-control status
4. check output (db offline)
  
Actual results:
bash-3.2$ db-control stop && db-control status
Shutting down database... done.
The database is in the process of shutting down.
bash-3.2$ sleep 10s && db-control status
The database is offline.

Expected results:
bash-3.2$ db-control stop && db-control status
Shutting down database... done.
The database is offline.
==== OR ====
mentioned in documentation, that 'db-control stop' only starts shutdown process and if necessary, sleep NN must be called before "db-control backup|restore" will be executed.

Additional info:
Comment 2 Miroslav Suchý 2012-03-23 14:53:57 UTC 
Fixed in satellite.git commit 695b00a
Comment 9 Clifford Perry 2013-10-01 21:58:55 UTC 
Satellite 5.6 has been released. This bug was tracked under the release.  

This bug was either VERIFIED or RELEASE_PENDING (re-verified prior shortly
before release). 

Moving to CLOSED CURRENT_RELEASE. 

Text from Upgrade Erratum follows:

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

http://rhn.redhat.com/errata/RHEA-2013-1395.html