Hide Forgot
Description of problem: Similar to Bug 1351753 which requests the ability for director to redeploy an existing controller node, my customer would like the ability to redeploy an existing compute node. Version-Release number of selected component (if applicable): OSP 8 director How reproducible: Very Steps to Reproduce: 1. Deploy HA overcloud with predictable hostnames and ips 2. Attempt to replace one of the controllers with another controller using the same hostname and ips. Additional info: The onsite consultant has tried various scenarios of nova delete, ironic delete, service delete to get the node to rebuild with the same name for a compute node. The only way he got it to rebuild a node was to completely remove it, and deploy with the next number in sequence, and leave a skip for the old node name. This is not the behavior that the customer would like.
The customer has asked if there are any suggestions from engineering on how to achieve this with a workaround while we wait for implementation of this RFE?
Following up to see if there are any updates on this for the workaround while this RFE is implemented.
From Customer recent comments, the automation Red Hat has developed (based on Director) doesn’t have provision for building a compute node with specific hostname – it only counts up starting at 0. So if we have 10 compute nodes and compute node 7 fails we can build node 11 but not node 7 if that makes sense. Is there another procedure we could employ to rebuild or otherwise replace a specific compute host?