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.

Bug 1545001

Summary: Document the addition of the '-y' flag to the katello-backup command
Product: Red Hat Satellite Reporter: Andrew Dahms <adahms>
Component: Docs Server Administration GuideAssignee: Russell Dickenson <rdickens>
Status: CLOSED CURRENTRELEASE QA Contact: Melanie Corr <mcorr>
Severity: medium Docs Contact:
Priority: medium    
Version: 6.2.13CC: bmidwood, brubisch, cfouant, hshukla, jomitsch, rhbgs.10.bigi_gigi
Target Milestone: Unspecified   
Target Release: Unused   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2018-03-04 22:50:04 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:

Description Andrew Dahms 2018-02-14 01:30:32 UTC
Red Hat Satellite 6.2.14 introduced a '-y' flag to the katello-backup command that changed the default behaviour. Now, users must supply this flag when running an off-line backup to ensure services are stopped when the backup is created.

The following section of the 6.2 Server Administration Guide must be updated to reflect the new behaviour -

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

Comment 1 Andrew Dahms 2018-02-14 01:31:32 UTC
Assigning to Russell for review.

Russell - we'll tackle these changes in the 6.2 version to start with given that this is where the greatest need is right now. When the 6.3 version has been fully converted to AsciiDoc, we can look to making the changes there as well, perhaps under a separate bug.

Comment 8 Bengt Giger 2018-02-26 12:17:50 UTC
The question should be avoided when the scripts runs non interactive. Currently, non interactive and offline mode, the script assumes "no" and continues. Consequently, the backup is performed with the services still running, leading to backups guaranteed to being corrupt, without feedback to the user. It took us 2 weeks and an analysis of the backup code until we discovered we had nothing but useless backups.

The script MUST either cancel and return an error code, or unconditionally stop the services if in offline mode, assuming that the selection of the offline mode implicates services stopped; IMHO using offline mode implicates stopping the services.

Please check how the currently broken script will be fixed before documenting.

Btw. the flag was introduced with 6.2.13

Comment 9 John Mitsch 2018-02-26 14:06:44 UTC
> The question should be avoided when the scripts runs non interactive.
> Currently, non interactive and offline mode, the script assumes "no" and
> continues. 

To make sure I understand, you are running the script with -y but not using --online-backup flag, and the script keeps the services running? If this is the case, we definitely need to file a bug around this. What version of satellite?

Comment 10 Bengt Giger 2018-02-27 16:49:57 UTC
No, with "-y" it behaves as designed. But doing offline backups in a non interactive script environment without the "-y" flag (which was the default up to 6.2.12) must either stop the services or return an error code. Not continue silently with the worst decicion: doing backup while the services are running. Customer scripts migrating from 6.2.12 do not set a "-y" flag.

I'm in touch with David Caplan about this issue, because two modifications introduced with 6.2.13 had disastrous effects on backup script implementations. I'm sure there are Satellite customer still running backup scripts which produces corrupt backups every day, unnoticed, because of the dangerous act of introducing this new flag. I just want to make sure that the documentation takes into account upcoming changes.