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

Bug 527200

Summary:	`db-control restore` have exit code 1 even when everything seems to be OK
Product:	Red Hat Satellite 5	Reporter:	Jan Hutař <jhutar>
Component:	Server	Assignee:	Jan Pazdziora (Red Hat) <jpazdziora>
Status:	CLOSED DUPLICATE	QA Contact:	Red Hat Satellite QA List <satqe-list>
Severity:	low	Docs Contact:
Priority:	low
Version:	530	CC:	cperry, jpazdziora
Target Milestone:	---
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2010-12-10 21:08:51 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:	462714

Description Jan Hutař 2009-10-05 10:14:02 UTC

Description of problem:
When I restore DB, `db-control restore` have exit code 1 even when everything seems to be OK.


Version-Release number of selected component (if applicable):
spacewalk-dobby-0.5.23-28.el5sat


How reproducible:
1 of 1 attempt


Steps to Reproduce:
1. $ db-control restore /tmp/backup/
2. $ echo $?


Actual results:
Return code is 1, even when everything seems to be OK


Expected results:
Return code should be 0, as everything seems to be OK


Additional info:
$ db-control restore /tmp/backup/
  [...]
  /tmp/backup/arch_1_1.arc.gz -> /rhnsat/admin/rhnsat/archive/arch_1_1.arc.tmp... done.  Checksum verified.
Extraction and verification complete, renaming files... done.
Removing unnecessary files... done.
Restoration complete, you may now start the database.
-bash-3.2$ echo $?
1

Comment 1 Jan Pazdziora (Red Hat) 2010-12-10 21:07:24 UTC

Taking.

Comment 2 Jan Pazdziora (Red Hat) 2010-12-10 21:08:51 UTC


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