Bug 1544401

Summary:	k-backup fails when passed a relative path for the destination
Product:	Red Hat Satellite	Reporter:	Evgeni Golov <egolov>
Component:	Backup & Restore	Assignee:	Evgeni Golov <egolov>
Status:	CLOSED ERRATA	QA Contact:	jcallaha
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	6.3.0	CC:	bkearney, ehelms, mmccune
Target Milestone:	Unspecified	Keywords:	Regression, Triaged
Target Release:	Unused
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Known Issue
Doc Text:	Known Issue Running `katello-backup` with a relative path for the destination, for example `katello-backup .', causes an error. Workaround Run `katello-backup` with a full path. For example 'katello-backup /backup-destination'.	Story Points:	---
Clone Of:	1544396
Clones:	1557333 (view as bug list)		Environment:
Last Closed:	2018-04-13 13:29:48 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:	1544396, 1553882, 1553883
Bug Blocks:	1557333

Comment 4 jcallaha 2018-03-26 17:30:11 UTC

Verified in Satellite 6.3.1.


-bash-4.2# pwd
/tmp

-bash-4.2# mkdir backup

-bash-4.2# katello-backup backup

DEPRECATION WARNING: katello-backup is deprecated and will
be removed in the next Satellite release. It is being replaced by
satellite-backup. Redirecting to satellite-backup now.

Starting backup: 2018-03-26 19:15:37 +0200
Creating backup folder /tmp/backup/satellite-backup-20180326191537
Generating metadata ... 
Done.
Backing up config files... 
Done.

...

Done with backup: 2018-03-26 19:18:16 +0200
**** BACKUP Complete, contents can be found in: /tmp/backup/satellite-backup-20180326191537 ****


-bash-4.2# ll backup/
total 0
drwxrwx---. 2 root postgres 203 Mar 26 19:18 satellite-backup-20180326191537

Comment 6 errata-xmlrpc 2018-04-13 13:29:48 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:1126