Bug 1399244
Summary: | katello-backup --online-backup shuts down satellite | |||
---|---|---|---|---|
Product: | Red Hat Satellite | Reporter: | Michael Arbet <marbet> | |
Component: | Backup & Restore | Assignee: | Christine Fouant <cfouant> | |
Status: | CLOSED ERRATA | QA Contact: | Peter Ondrejka <pondrejk> | |
Severity: | urgent | Docs Contact: | ||
Priority: | urgent | |||
Version: | 6.2.8 | CC: | bbuckingham, bkearney, cfouant, daniele, egolov, ehelms, jcallaha, ktordeur, ldelouw, oshtaier, pdwyer, pgozart, riehecky, rvdwees, sreber, swadeley, zhunting | |
Target Milestone: | Unspecified | Keywords: | Triaged, UserExperience | |
Target Release: | Unused | |||
Hardware: | x86_64 | |||
OS: | Linux | |||
URL: | http://projects.theforeman.org/issues/15454 | |||
Whiteboard: | ||||
Fixed In Version: | katello-3.0.0-18 | Doc Type: | If docs needed, set a value | |
Doc Text: | Story Points: | --- | ||
Clone Of: | ||||
: | 1426399 1431533 (view as bug list) | Environment: | ||
Last Closed: | 2017-05-01 13:56:27 UTC | Type: | Bug | |
Regression: | --- | Mount Type: | --- | |
Documentation: | --- | CRM: | ||
Verified Versions: | Category: | --- | ||
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | ||
Cloudforms Team: | --- | Target Upstream Version: | ||
Embargoed: | ||||
Bug Depends On: | 1417372, 1426413 | |||
Bug Blocks: | 1426399, 1431533, 1439123 |
Description
Michael Arbet
2016-11-28 15:58:21 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 sorry for typo: --online-backup option I should have said in comment 5 (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. *** Bug 1430736 has been marked as a duplicate of this bug. *** Verified in Sat 6.2.9-1, katello-backup no longer shuts down services with --online-backup option 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 |