Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1426563

Summary: [RFE][docs][director] OSPd replace real node - same IP and same name
Product: Red Hat OpenStack Reporter: Edu Alcaniz <ealcaniz>
Component: documentationAssignee: RHOS Documentation Team <rhos-docs>
Status: CLOSED WONTFIX QA Contact: RHOS Documentation Team <rhos-docs>
Severity: high Docs Contact:
Priority: high    
Version: 8.0 (Liberty)CC: athomas, bnemec, brault, dbecker, dmacpher, ealcaniz, emacchi, gbarros, gcharot, jcoufal, mburns, mcornea, morazi, rhel-osp-director-maint, shardy, srevivo
Target Milestone: asyncKeywords: FutureFeature, Triaged, ZStream
Target Release: 10.0 (Newton)   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-07-25 01:55:58 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: 1419948    

Description Edu Alcaniz 2017-02-24 10:17:43 UTC 
Description of problem:
Despite that it is not the cloud mentality. 
We are looking for RFE to replace real node, with same IP and same name that we already deployed.


https://access.redhat.com/documentation/en-us/red_hat_openstack_platform/8/html-single/director_installation_and_usage/#sect-Scaling_the_Overcloud

Replace node need to configure same IP and name for network, monitoring and customer is looking a real replace of one node. The documentation doesn't explain how to do it and it get other IPs and names. 

Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:
Comment 1 Ben Nemec 2017-03-30 14:39:15 UTC 
The problem is that it didn't work, at least last time I tried it: https://bugzilla.redhat.com/show_bug.cgi?id=1351753

I haven't been able to try it more recently so I'm not sure whether that's still an issue, but that's why it isn't documented.
Comment 2 Edu Alcaniz 2017-04-05 12:52:22 UTC 
Could you update to us about this RFE please.
Comment 4 Ben Nemec 2017-04-27 16:41:17 UTC 
Okay, this is now working in OSP 8, so I'm transferring it to the docs team as there are no functional changes needed to enable it.

For reference, the additional steps required to replace with the same hostname and ips were:

1) Add a new HostnameMap entry for overcloud-controller-3 that matches the removed controller.
2) Add an entry to the end of the IP lists in the ControllerIPs parameter from the ips-from-pool-all.yaml environment that matches the IP of the removed controller.

Note that nothing should be removed from the environment files.  The list of IPs should contain four entries in order for everything to line up.

If predictable hostnames are not in use I'm not sure this can be done.  I think the HostnameMap must be used in order to duplicate a previously used hostname.  If they were not used in the initial deployment though, it may be possible to add an environment that only maps overcloud-controller-3 to the replaced node's hostname.  I believe that should work in theory, but I haven't tested it.