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 1459632 - [RFE] Add instructions to show exactly how to retire old Sat5 and attach it's subscription to new Sat6
Summary: [RFE] Add instructions to show exactly how to retire old Sat5 and attach it's...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Docs Transition Guide
Version: Unspecified
Hardware: All
OS: Linux
low
low
Target Milestone: Unspecified
Assignee: Sergei Petrosian
QA Contact: Stephen Wadeley
URL:
Whiteboard:
Depends On:
Blocks: 1470081
TreeView+ depends on / blocked
 
Reported: 2017-06-07 16:12 UTC by Billy Holmes
Modified: 2019-09-26 18:03 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Enhancement
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-10-12 16:51:55 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Billy Holmes 2017-06-07 16:12:29 UTC
Document URL: 

https://access.redhat.com/documentation/en-us/red_hat_satellite/6.2/html/transition_guide/

Section Number and Name:

CHAPTER 3. TRANSITIONING FROM SATELLITE 5 TO 6

Describe the issue: 

Scenario:
1) The customer has INSTALLED a parallel Sat6 server using the Transition SKU

2) The customer has SETUP the new Sat6 server using various methods, but all needed attributes, organizations, locations, users, content views, repos, content, host groups, and other metadata is fully configured and operational.

3) The customer has MIGRATED all clients to the Satellite 6 server

4) The customer is ready to RETIRE the old Satellite 5 server.

Issue:
Instructions are missing that describe to the customer how to unregister the old Sat5 server and attach the real satellite subscription to the new Sat6 server.

Suggestions for improvement:

[Add text or a section with something like]

3.7 Retiring the old Satellite 5 server and disposing of the Transition SKU

On the customer portal:
* delete the real Satellite entitlement from the old Sat5 server
* delete the transition entitlement from the new Sat6 server
* attach the real Satellite entitlement to the new Sat6 server

On the new Sat6 server:
* run "subscription_manager refresh"
* or wait 24 hrs, but the refresh will fire it immediately.
* Ensure all the right channels are enabled/disabled.

Additional information: 
I couldn't find anything in the guides that say "this is how you retire the old Sat server and place the right entitlement on the new Satellite server."

Comment 1 Andrew Dahms 2017-06-22 04:04:56 UTC
Assigning to Sergei for review.

Sergei - this is a new section that we will need for the Transition Guide, and will require a little conceptual information and some investigation of the procedures in the Satellite 5 documentation as well.

I propose that we add the new section as outlined above, with an introduction that explains what the procedure is and when to run it (to decommission the old environment - not a requirement, but an optional step to clean everything up) - and the main steps themselves.

For each of the steps above, we'll need to look at the Transition Guide, then the Satellite 5 documentation such as the Installation Guide to see how these things are set up, then provide steps to delete them instead.

Let me know if you have any questions!

Comment 31 Andrew Dahms 2017-12-11 01:50:58 UTC
Updating the target milestone to reflect the time frame in which this work was completed.

Comment 33 Andrew Dahms 2018-01-16 00:33:56 UTC
Updating the doc type.


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