Comment 3 for bug 1605500

The issue reported on Sarath's setup with build 3 described in this bug is not due to openstack roles or vcenter-only mode ignored (as in the description).

The error seems to be due to missing setup-vcenter-plugin.
2016-07-21 23:23:15:454006: [root@10.87.26.197] sudo: setup-vcenter-plugin --vcenter_url 10.84.22.110 --vcenter_username <email address hidden> --vcenter_password Contrail123! --vcenter_datacenter datacenter --vcenter_dvswitch dvs2-mini4 --vcenter_ipfabricpg contrail-fab-pg --api_hostname 172.16.80.2 --api_port 8082 --zookeeper_serverlist 172.16.80.2:2181,172.16.80.13:2181,172.16.80.4:2181 --vcenter_mode vcenter-only
2016-07-21 23:23:15:456818: [root@10.87.26.197] out: [localhost] local: ln -sf /bin/true /sbin/chkconfig
2016-07-21 23:23:15:590154: [root@10.87.26.197] out: [localhost] local: sudo mv /tmp/tmpDyMbcj/contrail-vcenter-plugin.conf /etc/contrail/contrail-vcenter-plugin.conf
2016-07-21 23:23:15:593572: [root@10.87.26.197] out: [localhost] local: sudo vcenter-plugin-setup.sh
2016-07-21 23:23:15:601020: [root@10.87.26.197] out: contrail-vcenter-plugin: unrecognized service
2016-07-21 23:23:15:616550: [root@10.87.26.197] out:
2016-07-21 23:23:15:616661: [root@10.87.26.197] out: Fatal error: local() encountered an error (return code 1) while executing 'sudo vcenter-plugin-setup.sh'

This might be because of the vcenter-plugin not installed on 10.87.26.197. I was not able to see this issue on my single node setup with build 3, will triage if this is reported happening again.

-Amudha