Comment 2 for bug 1823396

This problem is almost certainly happening because the re-install will cause the worker node to attempt to join the cluster (with kubadm join). This will fail because the node still exists in kubernetes. The solution is likely to have sysinv delete the node when the re-install is done. We are already doing this when the node is deleted.