Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
Red Hat Satellite engineering is moving the tracking of its product development work on Satellite to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "Satellite project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs will be migrated starting at the end of May. If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "Satellite project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/SAT-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Description of problem:
The katello-backup script calls tar to create backups. If tar is failing, i.e. No space left on device or i.e by just killing the tar process, the backup script returns zero.
As a consequence, the failure of the backups is not reported, in contrary all is looking fine. A restore attempt will fail.
Version-Release number of selected component (if applicable):
katello-common-2.2.0.18-1.el7sat.noarch
How reproducible:
Always
Steps to Reproduce:
1./usr/bin/katello-backup /to/small/filesystem
2. tar: Removing leading `/' from member names
gzip: stdout: No space left on device
Done.
Backing up mongo db...
tar: Removing leading `/' from member names
gzip: stdout: No space left on device
Done.
[..]
**** BACKUP Complete, contents can be found in: /backup ****
[root@sat ~]#
3. echo $?
Actual results:
0
Expected results:
1 (or anything else non-zero
Additional info:
The script should look something like:
tar --selinux -czf config_files.tar.gz ${CONFIGS[*]} || exit $? to catch the exit code of tar
Comment 10Satellite Program
2018-02-21 16:54:37 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/RHSA-2018:0336
Description of problem: The katello-backup script calls tar to create backups. If tar is failing, i.e. No space left on device or i.e by just killing the tar process, the backup script returns zero. As a consequence, the failure of the backups is not reported, in contrary all is looking fine. A restore attempt will fail. Version-Release number of selected component (if applicable): katello-common-2.2.0.18-1.el7sat.noarch How reproducible: Always Steps to Reproduce: 1./usr/bin/katello-backup /to/small/filesystem 2. tar: Removing leading `/' from member names gzip: stdout: No space left on device Done. Backing up mongo db... tar: Removing leading `/' from member names gzip: stdout: No space left on device Done. [..] **** BACKUP Complete, contents can be found in: /backup **** [root@sat ~]# 3. echo $? Actual results: 0 Expected results: 1 (or anything else non-zero Additional info: The script should look something like: tar --selinux -czf config_files.tar.gz ${CONFIGS[*]} || exit $? to catch the exit code of tar