Bug 1243656 - [RFE] Document simplest steps for transferring host to new organization
Summary: [RFE] Document simplest steps for transferring host to new organization
Keywords:
Status: CLOSED DUPLICATE of bug 1366487
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Documentation
Version: 6.0.8
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: Unspecified
Assignee: satellite-doc-list
QA Contact: satellite-doc-list
URL:
Whiteboard:
: 1265460 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-07-16 03:26 UTC by jnikolak
Modified: 2019-09-12 08:38 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Enhancement
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-02-01 06:22:57 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
screenshot1 (21.66 KB, image/png)
2015-07-16 03:26 UTC, jnikolak
no flags Details

Description jnikolak 2015-07-16 03:26:05 UTC
Created attachment 1052534 [details]
screenshot1

1. Proposed title of this feature request  
      
Add wizard when transferring host to new organization
      
    2. Who is the customer behind the request?  
    Account: name and acct # Telstra / 5568718
      
    TAM customer: yes  
    SRM customer: yes  
    Strategic:    yes  
      
    3. What is the nature and description of the request?  

To understand the RFE first try to reproduce:

1. Ensure that you have 2 organizations (we'll call them A and B), and a host assigned to organization A with host group A
2. Go to Hosts / All Hosts, tick the host and then go to Select Action / Assign Organization
3. Attempt to move the host to the new organization with "Fix Organization on Mismatch" 

When selecting this option, 

It should provide you with a Wizard option

i.e 

--> "Fix Organization on Mismatch" 
   -> Select Organization to transfer
      ->> Do you want to associate or create new hostgroup
          --> Specify Name of new Hostgroup
      ->> Create matching puppet modules  (yes/no)
          --> If No then  ..
          --> If yes then ...  
      ->> Create matching Activation keys (yes/no)
          --> If No then  ..
          --> If yes then ... 
      ->> Create New lifecycle environment (yes/no)
          --> If No then  ..
          --> If yes then ...   
      ->> If customer have Parent, Create matching parent (yes|no)

    4. Why does the customer need this? (List the business requirements here)  
So that if customer decies to move a host to a new organization, they will have more precise capabilities

    5. How would the customer like to achieve this? (List the functional requirements here)  
N/A
      
    6. For each functional requirement listed, specify how Red Hat and the customer can test to confirm the requirement is successfully implemented. 

n/a 
      
    7. Is there already an existing RFE upstream or in Red Hat Bugzilla?  
      
Not to my knowledge

    8. Does the customer have any specific timeline dependencies and which release would they like to target (i.e. RHEL5, RHEL6)?  
      
No

    9. Is the sales team involved in this request and do they have any additional input?  

No
      
    10. List any affected packages or components.  
      
    11. Would the customer be able to assist in testing this functionality if implemented?  

Yes

Comment 1 RHEL Program Management 2015-07-16 03:45:24 UTC
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 4 Deon Ballard 2015-12-02 19:35:28 UTC
Mass re-assign of all content / lifecycle related bugs to Dan MacPherson for the new content management guide.

Comment 5 Deon Ballard 2015-12-10 17:21:14 UTC
++++ IMPORTANT +++++

These bugs are being reassigned to Dan MacPherson as part of his work on creating a content management guide.


/////////////////////////////
DO NOT REASSIGN TO THE QUEUE.
/////////////////////////////

Comment 6 Andrew Dahms 2016-12-02 00:48:42 UTC
*** Bug 1265460 has been marked as a duplicate of this bug. ***

Comment 7 Andrew Dahms 2016-12-02 00:49:27 UTC
Moving back to the default assignee to be re-triaged as the schedule allows.

Comment 8 Andrew Dahms 2017-02-01 06:22:57 UTC
This issue has also been reported in BZ#1366487, to which an open customer case is currently attached.

I will close this bug as a duplicate, and work to address this request shall be tracked in the above bug going forward.

Kind regards,

Andrew

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


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