Bug 1152797 - [RFE] Provide Documentation to update Satellite FQDN and associated certificates (rename a Satellite)
[RFE] Provide Documentation to update Satellite FQDN and associated certifica...
Status: CLOSED DUPLICATE of bug 924383
Product: Red Hat Satellite 6
Classification: Red Hat
Component: Docs Install Guide (Show other bugs)
6.0.4
Unspecified Unspecified
medium Severity medium (vote)
: Unspecified
: 6.2
Assigned To: satellite-doc-list
satellite-doc-list
: FutureFeature
: 1181276 1181283 1213912 (view as bug list)
Depends On: 924383 1480346
Blocks: GSS_Sat6Beta_Tracker/GSS_Sat6_Tracker sat61-release-notes
  Show dependency treegraph
 
Reported: 2014-10-14 21:22 EDT by Rich Jerrido
Modified: 2017-08-11 03:59 EDT (History)
16 users (show)

See Also:
Fixed In Version:
Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2016-08-04 11:47:52 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 Knowledge Base (Solution) 1232133 None None None Never

  None (edit)
Description Rich Jerrido 2014-10-14 21:22:53 EDT
Document URL: https://access.redhat.com/documentation/en-US/Red_Hat_Satellite/6.0/html-single/Installation_Guide/index.html#Configuring_RednbspHat_Satellite_with_a_Custom_Server_Certificate

Section Number and Name: 2.3.2 - Configuring Red Hat Satellite with a Custom Server Certificate

Describe the issue: 

This RFE requests adding a section within the installation guide that covers how to change the fully qualifed domain name of a Satellite 6 instance, and update any/all SSL certificates to match the new hostname. 

This would ideally be placed as a chapter/section after section 2.3.2, as the other custom SSL certificate content is placed there. 


Suggestions for improvement: 

Additional information: 

This process is currently documented in the following KCS [https://access.redhat.com/solutions/1232133]
Comment 1 RHEL Product and Program Management 2014-10-14 21:42:54 EDT
Since this issue was entered in Red Hat Bugzilla, the release flag has been
set to ? to ensure that it is properly evaluated for this release.
Comment 3 Athene Chan 2014-10-14 23:43:17 EDT
Thanks Rich! Adding to the requests queue!
Comment 13 RHEL Product and Program Management 2015-04-21 12:09:52 EDT
Since this issue was entered in Red Hat Bugzilla, the release flag has been
set to ? to ensure that it is properly evaluated for this release.
Comment 18 Hayley Hudgeons 2015-10-20 16:35:10 EDT
*** Bug 1181276 has been marked as a duplicate of this bug. ***
Comment 21 Mike McCune 2015-11-04 18:54:39 EST
ALL:

There is no supported or tested routine for changing your Satellite 6.0 or 6.1 hostname. This will need to be added in Satellite 6.2 and should not be referenced in documentation or worked on until development of this feature is complete.

I also stated this very publicly here:

https://access.redhat.com/solutions/1315853
Comment 23 Mike McCune 2015-11-04 19:54:32 EST
correction, the correct KCS is:

https://access.redhat.com/solutions/1232133
Comment 24 Stephen Wadeley 2016-02-17 03:26:02 EST
Change flag to propose for 6.3, not 6.2, as the parent bug has just been changed:

 RHEL Product and Program Management 2016-02-16 15:07:19 EST
Flags: sat-6.3.0? → sat-6.3.0+
Comment 25 Kristof Van Damme 2016-04-14 11:03:10 EDT
A related question: is it possible to run Satellite 6 under a URL which is different from the hostname of the server it runs on ?
Comment 26 David O'Brien 2016-04-17 20:48:35 EDT
Reset docs contact <> daobrien
Comment 28 Stephen Benjamin 2016-07-29 10:12:35 EDT
*** Bug 1181283 has been marked as a duplicate of this bug. ***
Comment 29 Stephen Benjamin 2016-07-29 10:14:20 EDT
*** Bug 1213912 has been marked as a duplicate of this bug. ***
Comment 30 Mike McCune 2016-08-04 11:47:52 EDT

*** This bug has been marked as a duplicate of bug 924383 ***

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