Comment 0 for bug 1721834

Setup:-

nodem5 -- 10.204.216.94 -- all in one node

root@nodem5:/opt/contrail/server_manager/ansible/playbooks/r41newton10/playbooks# docker exec -it controller contrail-status
== Contrail Control ==
contrail-control: inactive (disabled on boot)
contrail-named: inactive (disabled on boot)
contrail-dns: inactive (disabled on boot)
contrail-control-nodemgr: inactive (disabled on boot)
== Contrail Config ==
contrail-api: inactive (disabled on boot)
contrail-schema: inactive (disabled on boot)
contrail-svc-monitor: inactive (disabled on boot)
contrail-device-manager: inactive (disabled on boot)
contrail-config-nodemgr: inactive (disabled on boot)
== Contrail Config Database==
contrail-database: inactive (disabled on boot)

== Contrail Web UI ==
contrail-webui: inactive (disabled on boot)
contrail-webui-middleware: inactive (disabled on boot)
== Contrail Support Services ==
zookeeper: inactive
rabbitmq-server: inactive (disabled on boot)
root@nodem5:/opt/contrail/server_manager/ansible/playbooks/r41newton10/playbooks#

root@nodem5:/# docker exec -it controller journalctl -u contrail-ansible
-- Logs begin at Fri 2017-10-06 17:29:17 IST, end at Fri 2017-10-06 22:16:55 IST. --
Oct 06 17:29:23 nodem5 systemd[1]: Starting Contrail controller configuration...
Oct 06 17:29:24 nodem5 contrailctl[22]: Additional properties are not allowed ('metadata_ssl_enable' was unexpected)
Oct 06 17:29:29 nodem5 systemd[1]: contrail-ansible.service: Main process exited, code=exited, status=1/FAILURE
Oct 06 17:29:29 nodem5 systemd[1]: Failed to start Contrail controller configuration.
Oct 06 17:29:31 nodem5 systemd[1]: contrail-ansible.service: Unit entered failed state.
Oct 06 17:29:31 nodem5 systemd[1]: contrail-ansible.service: Failed with result 'exit-code'.
root@nodem5:/#