Bug 924383

Summary: [RFE] Need a server side tool to assist with the process of changing the hostname of the Katello server
Product: Red Hat Satellite Reporter: Mike McCune <mmccune>
Component: InfrastructureAssignee: John Mitsch <jomitsch>
Status: CLOSED ERRATA QA Contact: Peter Ondrejka <pondrejk>
Severity: high Docs Contact:
Priority: high    
Version: 6.0.0CC: ahuchcha, ahumbe, aperotti, bart.baenisch, bbuckingham, bfinger, bkearney, chrobert, djuran, dkaylor, dsulliva, egolov, ekin.meroglu, fgarciad, ftsiadim, greartes, hajek, jnikolak, jomitsch, jwildman, kdixon, ktordeur, mmccune, mmello, mverma, nobody, pmoravec, pmutha, pondrejk, riehecky, rjerrido, sthirugn, swadeley, taw, wharris, wpinheir, xdmoon, zhunting
Target Milestone: UnspecifiedKeywords: FutureFeature, PrioBumpGSS, Reopened, Triaged
Target Release: Unused   
Hardware: Unspecified   
OS: Unspecified   
URL: http://projects.theforeman.org/issues/17522
Whiteboard:
Fixed In Version: katello-3.0.0-26 Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of:
: 1480346 (view as bug list) Environment:
Last Closed: 2017-09-25 18:59:44 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:    
Bug Blocks: 1152797, 1190823, 1269671, 1385841, 1451564    
Attachments:
Description Flags
kickstart-sync-log none

Description Mike McCune 2013-03-21 16:14:09 UTC
Spacewalk has a tool called 'spacewalk-hostname-rename' that will update the certificates and configurations on the spacewalk server so it can be migrated to a new hostname.

We need this for katello as well.  The current process to change your Katello hostname is undocumented and painful.

Comment 2 Bryan Kearney 2014-06-13 15:27:51 UTC
See also: https://bugzilla.redhat.com/show_bug.cgi?id=876359

Comment 3 Mike McCune 2014-10-15 04:19:57 UTC
we have this now:

https://access.redhat.com/solutions/1232133

closing:currentrelease

Comment 4 Xixi 2014-10-22 23:13:01 UTC
(In reply to Mike McCune from comment #3)
> https://access.redhat.com/solutions/1232133

Documentation BZ tracking official doc inclusion:
Bug 1152797 - [RFE] Provide Method to update Satellite FQDN and associated certificates

Comment 6 David O'Brien 2014-12-10 12:36:52 UTC
https://access.redhat.com/solutions/1232133

Please refer to djuran's comments in this article. Procedure doesn't seem to work.

Comment 9 Eric Helms 2016-03-09 21:12:29 UTC
*** Bug 1222194 has been marked as a duplicate of this bug. ***

Comment 10 Pavel Moravec 2016-07-15 07:24:04 UTC
Does this BZ cover changing hostname of Satellite only, or also Capsule (there are customers with both requests)?

Comment 11 Mike McCune 2016-08-04 15:47:52 UTC
*** Bug 1152797 has been marked as a duplicate of this bug. ***

Comment 14 Bryan Kearney 2016-08-04 20:19:45 UTC
Moving 6.2 bugs out to sat-backlog.

Comment 16 John Mitsch 2016-11-29 21:04:28 UTC
Created redmine issue http://projects.theforeman.org/issues/17522 from this bug

Comment 19 Satellite Program 2017-01-25 21:03:41 UTC
Moving this bug to POST for triage into Satellite 6 since the upstream issue http://projects.theforeman.org/issues/17522 has been resolved.

Comment 21 John Mitsch 2017-04-27 17:50:43 UTC
Connecting redmine issue http://projects.theforeman.org/issues/18403 from this bug

Comment 33 John Mitsch 2017-09-14 17:37:35 UTC
I updated my MR to fix the installation media paths, peter tested it with success, it is now merged. 

I reviewed Evgeni's upstream PRs for the issues he mentioned, one is merged, one is waiting on a rebase, and the third is waiting on the contributor. Thanks Evgeni!

I'll submit an upstream PR for http://projects.theforeman.org/issues/20925 and link up these issues with this BZ. After these are merged we will be all set.

-John

Comment 38 Peter Ondrejka 2017-09-21 09:02:20 UTC
Created attachment 1328879 [details]
kickstart-sync-log

Comment 41 errata-xmlrpc 2017-09-25 18:59:44 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/RHBA-2017:2803