Created attachment 1150584 [details]
Screenshot of auto-detected fusor/director
Description of problem: When creating a 2nd deployment that uses the same undercloud as a previous deployment, autodetection allows registration of the fusor and/or director
Version-Release number of selected component (if applicable): TP3 RC4
How reproducible: 100%
Steps to Reproduce:
1. Create a deployment, register osp nodes using pxe_ssh and kick off deployment
2. Create a second deployment
3. Register the same undercloud used in previous deployment
4. Use auto detection to query the same pxe_ssh server as above
Actual results: The fusor and director machines used in the current deployment are options for node registration. Any OSP nodes already registered are missing (as expected)
Expected results: Fusor and director VMs should be absent for the auto-detection list
Please re-test, we intend to only support one deployment for each undercloud.
Per comment #1, I was able to delete and reuse the undercloud for a 2nd deployment using the WebUI. The previous nodes used for the overcloud were already registered and that registration was reflected in the WebUI.
I was still able to select the fusor and undercloud VMs during autodetection, I will mark this a VERIFIED. I submitted an RFE bug to disable fusor/undercloud nodes from selection during any node registration
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.