Bug 1439694 - katello-restore fails to restore a good backup
Summary: katello-restore fails to restore a good backup
Keywords:
Status: CLOSED DUPLICATE of bug 1433888
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Backup & Restore
Version: 6.2.8
Hardware: x86_64
OS: Linux
high
medium
Target Milestone: Unspecified
Assignee: Christine Fouant
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-04-06 12:09 UTC by gpizarro
Modified: 2017-05-22 15:34 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-05-22 15:34:14 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description gpizarro 2017-04-06 12:09:57 UTC
Description of problem:

katello-restore fails to restore a good full backup. After restoring pulp content, which works, it goes on to restore mongodb data and exits right away.


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

Satellite 6.2.8


How reproducible:

Always, in this system at least.


Steps to Reproduce:
1. Take full backup with katello-backup
2. Run katello-restore $BKPDIR
3. Wait until pulp content is restored


Actual results:

---
gzip: stdin: not in gzip format
tar: Child returned status 1
tar: Error is not recoverable: exiting now
---


Expected results:

The backup is restored and Satellite starts.


Additional info:

Looking at the katello-restore script I see the actual command used is this:

tar --selinux --overwrite --listed-incremental=/dev/null -xfz mongo_data.tar.gz -C /

The problem here is the 'z' switch. Tar can determine the format of the file to extract so it's not needed to start with. And since the file is _not_ compressed (see below) it makes it fail.

Moreover, looking at the katello-backup script I see that a filename with .gz extension is used in the tar commands for mongodb and postgresql, but the z switch is not used so a plain tar file is created. Then a gzip command is meant to compress the tar files, but they don't exist (they're tar.gz) and so they're never compressed. This step should simply be done in one go with the tar command adding -z.

Comment 2 Christine Fouant 2017-05-22 15:34:14 UTC

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


Note You need to log in before you can comment on or make changes to this bug.