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.
DescriptionJoniel Pasqualetto
2020-09-03 15:50:03 UTC
Description of problem:
when foreman-maintain backup offline fails, for example, during the backup of pulp content, the whole execution is simply aborted and services are not started again.
Version-Release number of selected component (if applicable):
How reproducible:
Always
Steps to Reproduce:
1. Ensure you can start the backup operation, but that you won't be able to export the full pulp-content (point to a directory with not enough free disk space, for example)
2. Launch the backup:
~~~
# foreman-maintain backup offline -y /boot/backup
(...)
Backup config files:
| Collecting config files to backup [OK]
--------------------------------------------------------------------------------
Backup Pulp data:
- Collecting Pulp data [FAIL]
Failed executing tar --selinux --create --file=/boot/backup/satellite-backup-2020-09-03-11-45-28/pulp_data.tar --exclude=var/lib/pulp/katello-export --listed-incremental=/boot/backup/satellite-backup-2020-09-03-11-45-28/.pulp.snar --transform 's,^,var/lib/pulp/,S' -S *, exit status 2:
tar: /boot/backup/satellite-backup-2020-09-03-11-45-28/pulp_data.tar: Wrote only 2048 of 10240 bytes
tar: Error is not recoverable: exiting now
--------------------------------------------------------------------------------
Scenario [Backup] failed.
The following steps ended up in failing state:
[backup-pulp]
Resolve the failed steps and rerun
the command. In case the failures are false positives,
use --whitelist="backup-pulp"
The runner is already in quit state
~~~
Actual results:
Services remain stopped and maintenance_mode is on (iptables rules enabled).
Expected results:
Services would be restarted and maintenance_mode disabled.
Additional info:
Comment 3Julio Entrena Perez
2021-03-29 08:36:27 UTC