The existing QA host (windchill-test) was set up as a Cluster Node in production pre-rehost. So when trying to make windchill-test the "new" host again, we got a duplicate key error from the fvHost table. I suppose this makes sense and perhaps we used the wrong approach if we just wanted to update the existing QA host with the latest production data?
We were unable to remove the Cluster Nodes during the rehost so we used a workaround by renaming them to "fake" hosts in order to be able to change the Standalone Node.
After we got all the services up again we were able to remove the cluster nodes from the front-end.
What I would like to know is whether it is going to be necessary to use this workaround each time we do a rehost?
Is the QA host supposed to be set up as a Cluster Node in production? We inherited this setup from the previous admin so not sure if this is best practice?
Should we have used a different rehost approach to just update the test environment with the latest production data?