Comment 4 for bug 1748065

We ended up having to change the order of the controllers specified in the multinode inventory file, which solved our issues. The inventory file was returned to its original state after controller001 was re-deployed successfully. So it appears that changing the order of the controllers in the multinode inventory file isn't too much of an issue, with the requirement that the first controller listed is a "working" node.

Eric