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 shuts down satellite services even if issued with parameter '--online-backup' - exactly opposite to the impression - it sounds like should keep the things running. When the backup is complete the services are back.
Version-Release number of selected component (if applicable):
How reproducible:
katello-backup --skip-pulp-content /var/backup
katello-backup --online backup --skip-pulp-content /var/backup
try to connect to satellite using browser and/or observe if port 443 is listening - it should be shut down in both cases
Expected results:
The second option --online-backup should keep satellite services running
Comment 3Satellite Program
2017-02-23 21:10:11 UTC
Please add verifications steps for this bug to help QE verify
(In reply to pm-sat from comment #3)
> Please add verifications steps for this bug to help QE verify
Verification steps:
1) Run katello-backup with the online-backup option (i.e. #katello-backup /tmp/backup --online-backup)
2) Verify that services stay online during the backup process.
Please let me know if you need anything else, thanks!
Hello
Does the service *stay* down after using --on-line option?
It is explained in the guide [1] that "the time consuming backup of the Pulp directory is performed on-line to reduce the time Satellite services are unavailable. Configuration files and databases are backed up off-line first."
and then later "The katello-backup script with the --online-backup option first stops all services which could impact the backup, backs up the configuration files and databases, restarts the required services, and then performs the more time consuming backup of the Pulp directory"
Is any of that incorrect at the moment?
Thank you
[1] https://access.redhat.com/documentation/en-us/red_hat_satellite/6.2/html/server_administration_guide/chap-red_hat_satellite-server_administration_guide-backup_and_disaster_recovery
(In reply to Stephen Wadeley from comment #5)
> Hello
>
>
> Does the service *stay* down after using --on-line option?
>
> It is explained in the guide [1] that "the time consuming backup of the Pulp
> directory is performed on-line to reduce the time Satellite services are
> unavailable. Configuration files and databases are backed up off-line first."
>
> and then later "The katello-backup script with the --online-backup option
> first stops all services which could impact the backup, backs up the
> configuration files and databases, restarts the required services, and then
> performs the more time consuming backup of the Pulp directory"
>
>
> Is any of that incorrect at the moment?
>
> Thank you
>
>
> [1]
> https://access.redhat.com/documentation/en-us/red_hat_satellite/6.2/html/
> server_administration_guide/chap-red_hat_satellite-
> server_administration_guide-backup_and_disaster_recovery
Yes, as the code currently stands, running katello-backup will shut down services regardless of whether or not the --online-backup option is used. However, if --online-backup is selected, the services never even start back up via the script.
Comment 10Christine Fouant
2017-03-10 16:47:36 UTC
*** Bug 1430736 has been marked as a duplicate of this bug. ***
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-2017:1191