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:
Katello-backup will shut down the satellite without prompting the user first. This can have serious consequences if the user does not know ahead of time that the satellite will be shut down during the backup.
Note that there is a --online-backup option, but it applies only to the Pulp portion. This should likely be renamed to --online-pulp-backup to avoid confusion.
Ideally, katello-backup would prompt the user before commencing the backup that there will be a shutdown, and have a command-line option to optionally skip the prompt (for example, --ok-to-shutdown or similar).
Version-Release number of selected component (if applicable): 6.2.6
The latest version from upstream properly keeps services online:
# ./katello-backup --skip-pulp-content --online-backup /var/tmp
Starting backup: 2017-01-20 13:15:09 -0500
Creating backup folder /var/tmp/katello-backup-2017-01-20T13:15:09-05:00
Backing up config files...
tar: Removing leading `/' from member names
Done.
Backing up postgres db...
Done.
Backing up mongo db...
Done.
Done with backup: 2017-01-20 13:21:53 -0500
**** BACKUP Complete, contents can be found in: /var/tmp/katello-backup-2017-01-20T13:15:09-05:00 ****
but we still need a confirm flag.
katello-backup does provide the message that it's being replaced by foreman-maintain backup as seen below:
-bash-4.2# katello-backup --skip-pulp-content --online-backup /var/tmp
IMPORTANT: katello-backup has been removed in favor of 'foreman-maintain backup'.
This change happened in order to support remote databases and a newer mongo version.
Please update your scripts and/or cron jobs.
Ran foreman-mantain backup and successfully backed up system with both online and offline options as seen below:
Done with backup: 2018-09-19 10:28:27 -0400
**** BACKUP Complete, contents can be found in: /var/tmp/satellite-backup-2018-09-19-10-24-58 ****
Marking this as