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

Bug 1360841

Summary:	`db-control backup` should log when it creates a backup and that log should be present in spacewalk-debug tarball
Product:	Red Hat Satellite 5	Reporter:	Jan Hutař <jhutar>
Component:	Server	Assignee:	Tomáš Kašpárek <tkasparek>
Status:	CLOSED ERRATA	QA Contact:	Lukáš Hellebrandt <lhellebr>
Severity:	low	Docs Contact:
Priority:	unspecified
Version:	unspecified	CC:	jdostal, ktordeur, lhellebr, tlestach
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	spacewalk-web-2.5.2-14-sat	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2018-02-05 13:57:18 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:	1450111

Description Jan Hutař 2016-07-27 15:45:43 UTC

Description of problem:
`db-control backup` should log when it creates a backup and that log should be present in spacewalk-debug tarball


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


How reproducible:
always


Steps to Reproduce:
1. # db-control backup
2. # db-control online-backup


Actual results:
It is not logged anywhere


Expected results:
Successful run should be recorded somewhere

Comment 2 Tomáš Kašpárek 2017-10-16 13:03:28 UTC

db-control already logs into /var/log/rhn/rhn_database.log which is packed with spacewalk-debug, I've just extended it by a bit to see whether the action completed successfully or not

spacewalk.git(master): 372963d390ce0ffa0b1cfb9591d4a12ddf0b703c

Comment 5 Lukáš Hellebrandt 2018-01-16 13:28:11 UTC

FailedQA with spacewalk-web-2.5.2-14.

db-control is indeed logged in /var/log/rhn/rhn_database.log. However, regardless of whether it completed successfully or unsuccessfully, it always says "Completed: db-control [...]" so there is no way to determine whether the backup was actually done or it failed. Please, just make the output say something about failure in case $?!=0.

Comment 6 Lukáš Hellebrandt 2018-01-16 13:32:27 UTC

Verified with spacewalk-web-2.5.2-14.

1) # db-control backup
2) # spacewalk-debug
3) untar + unbzip the resulting archive
4) # grep backup rhn_logs/rhn/rhn_database.log
5) ^ check time, it should be a few seconds ago when you ran the backup
6) repeat for db-control online-backup

In case of successful run, the log says "Invocation:" and then "Completed:" while in case of unsuccessfull run, it only says "Invocation:".

Comment 9 errata-xmlrpc 2018-02-05 13:57:18 UTC

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.

https://access.redhat.com/errata/RHBA-2018:0274