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 1488590

Summary: Rename katello-backup, katello-restore, and katello-change-hostname as satellite-* tools
Product: Red Hat Satellite Reporter: John Mitsch <jomitsch>
Component: Backup & RestoreAssignee: John Mitsch <jomitsch>
Status: CLOSED ERRATA QA Contact: Jan Hutaƙ <jhutar>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 6.2.0CC: bbuckingham, bkearney, jhutar, pondrejk, rnuccite
Target Milestone: UnspecifiedKeywords: Triaged
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-02-21 17:04:07 UTC Type: ---
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: 1482164    
Bug Blocks: 1376968, 1482166    

Description John Mitsch 2017-09-05 19:10:35 UTC
We can break out katello-change-hostname, katello-restore, and katello-backup into classes and that will make it easier for use to test and update names on backports.

Comment 1 John Mitsch 2017-09-05 19:10:38 UTC
Created from redmine issue http://projects.theforeman.org/issues/20821

Comment 2 John Mitsch 2017-09-05 19:10:41 UTC
Upstream bug assigned to jomitsch

Comment 4 John Mitsch 2017-09-19 15:51:17 UTC
*** Bug 1482135 has been marked as a duplicate of this bug. ***

Comment 5 Peter Ondrejka 2017-10-16 09:44:30 UTC
Working on related bugs https://bugzilla.redhat.com/show_bug.cgi?id=1497957
https://bugzilla.redhat.com/show_bug.cgi?id=1482168 I found all tree scripts fail with missing ruby scripts, e.g.:

~]# katello-change-hostname -h

DEPRECATION WARNING: katello-change-hostname is deprecated and will
be removed in the next Satellite release. It is being replaced by
satellite-change-hostname. Redirecting to satellite-change-hostname now.

/usr/share/rubygems/rubygems/core_ext/kernel_require.rb:55:in `require': cannot load such file -- /usr/sbin/hostname-change.rb (LoadError)
	from /usr/share/rubygems/rubygems/core_ext/kernel_require.rb:55:in `require'
	from /usr/sbin/satellite-change-hostname:10:in `<main>'


Also, about the DEPRECATION WARNING, are we really going to remove the thing in next release, why? Redirect is in place, I don't see any risk in keeping the legacy option functional. Also, is there a documentation bug about this change?

Comment 8 Peter Ondrejka 2017-10-17 09:30:06 UTC
docs bug created https://bugzilla.redhat.com/show_bug.cgi?id=1503054

Comment 10 Bryan Kearney 2018-02-21 17:04:07 UTC
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/RHSA-2018:0336