Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 1569672 - Deprecate katello-backup, and katello-restore in Satellite 6.3
Deprecate katello-backup, and katello-restore in Satellite 6.3
Status: CLOSED ERRATA
Product: Red Hat Satellite 6
Classification: Red Hat
Component: Backup & Restore (Show other bugs)
Unspecified
Unspecified Unspecified
unspecified Severity high (vote)
: 6.3.4
: Unused
Assigned To: John Mitsch
jcallaha
: Triaged
Depends On: 1567884
Blocks:
  Show dependency treegraph
 
Reported: 2018-04-19 14:36 EDT by John Mitsch
Modified: 2018-10-11 11:18 EDT (History)
7 users (show)

See Also:
Fixed In Version: satellite-6.3.4-2
Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2018-10-11 11:18:07 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)


External Trackers
Tracker ID Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2018:2915 None None None 2018-10-11 11:18 EDT

  None (edit)
Description John Mitsch 2018-04-19 14:36:09 EDT
Description of problem:

katello-service, katello-backup, and katello-restore functionality is going to be in foreman-maintain in 6.4. The original katello-* and satellite-* scripts will still live in 6.4, but we should deprecate them and remove them in 6.5 since they will be removed upstream.

Version-Release number of selected component (if applicable):
6.4
Comment 2 John Mitsch 2018-04-30 16:11:51 EDT
After a off-thread discussion, we have decided to remove the original katello-backup/restore scripts in 6.4 and deprecate them in 6.3.

Brad, can you update the flags for 6.3?
Comment 3 Mike McCune 2018-04-30 16:20:22 EDT
this would be 6.3.z only with a DEPRECATION WARNING in the output of katello-backup/restore but have zero effect on the actual functionality of the 2 tools.
Comment 12 jcallaha 2018-09-24 13:41:51 EDT
Verified in Satellite 6.3.4 Snap 2


-bash-4.2# satellite-backup --help
DEPRECATION WARNING: satellite-backup and katello-backup will be removed in Satellite 6.4, where they will be replaced by foreman-maintain
Usage: satellite-backup /path/to/dir [options]
 eg: $ satellite-backup /tmp/satellite-backup
        --skip-pulp-content          Create backup without Pulp content for debugging only
        --incremental PREVIOUS_BACKUP_DIR
                                     Backup changes since previous backup
        --online-backup              Keep services online during backup
        --logical-db-backup          Also dump full database schema during offline backup
        --snapshot                   Use snapshots of the databases to create backup
        --snapshot-mount-dir SNAPSHOT_MOUNT_LOCATION
                                     Override default directory (/var/snap/) where the snapshots will be mounted
        --snapshot-size SNAPSHOT_BLOCK_DEVICE_SIZE
                                     Override default block size (2G)
        --features FEATURES          Capsule features to include in the backup, please specify a list with commas. Valid features are tftp, dns, dhcp, openscap, and all.
        --preserve-directory         Do not create a time-stamped subdirectory
    -y, --assumeyes                  Bypass interaction by answering yes



-bash-4.2# satellite-restore --help
DEPRECATION WARNING: satellite-restore and katello-restore will be removed in Satellite 6.4, where they will be replaced by foreman-maintain
Usage: satellite-restore /path/to/dir [options]
 eg: $ satellite-restore /tmp/backup/satellite-backup-20171002150106
    -i, --incremental                Restore an incremental backup
    -y, --assumeyes                  Answer yes for all questions
Comment 14 errata-xmlrpc 2018-10-11 11:18:07 EDT
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-2018:2915

Note You need to log in before you can comment on or make changes to this bug.