Comment 2 for bug 1786520

I looked into this failure a while back when we reparented the zuul jobs:

http://logs.openstack.org/76/581376/6/check/tripleo-ci-centos-7-3nodes-multinode/4708903/logs/undercloud/home/zuul/overcloud_deploy.log.txt.gz#_2018-07-12_22_59_54

Basically ... ControllerApi/centos-7-inap-mtl01-0000693370/UpgradeInitDeployment does not exist - ControllerApi/centos-7-inap-mtl01-0000693368/UpgradeInitDeployment does

Looking at http://logs.openstack.org/76/581376/6/check/tripleo-ci-centos-7-3nodes-multinode/4708903/logs/undercloud/home/zuul/hostnamemap.yaml.txt.gz - it is confusing overcloud-controllerapi-0: centos-7-inap-mtl01-0000693368 and overcloud-controller-0: centos-7-inap-mtl01-0000693370

This is the failing line:
https://github.com/openstack/tripleo-common/blob/master/tripleo_common/templates/deployments.yaml#L3

The nodes file: https://github.com/openstack/tripleo-quickstart/blob/master/config/nodes/2ctlr.yml relies on the nodes to be assigned in a particular order. Sometimes this works out and sometimes it does not