And here is a test case for this bug:
1) Remove a primary-controller node from environment, and deploy
2) Add a new controller, and deploy
3) repeat the steps 1-2 until some of the old node name swill be reused for a new node
4) verify output of ls -ld /var/log/remote/* | awk '{ print $11 }' | sort | uniq -d
it should give nothing (test passed), otherwise it will print the names of affected nodes
And here is a test case for this bug:
1) Remove a primary-controller node from environment, and deploy
2) Add a new controller, and deploy
3) repeat the steps 1-2 until some of the old node name swill be reused for a new node
4) verify output of ls -ld /var/log/remote/* | awk '{ print $11 }' | sort | uniq -d
it should give nothing (test passed), otherwise it will print the names of affected nodes