Contrail :: 16.04 10 newton :: provisioning failed due to metadata ssl parameter validation.
Affects | Status | Importance | Assigned to | Milestone | ||
---|---|---|---|---|---|---|
Juniper Openstack | Status tracked in Trunk | |||||
R4.0 |
Fix Committed
|
Critical
|
Nitish Krishna Kaveri | |||
R4.1 |
Fix Committed
|
Critical
|
Nitish Krishna Kaveri | |||
Trunk |
Fix Committed
|
Critical
|
Nitish Krishna Kaveri |
Bug Description
Metadata ssl variable schema validation needs to be implemented in contrail docker repo.
Setup:-
nodem5 -- 10.204.216.94 -- all in one node
root@nodem5:
== Contrail Control ==
contrail-control: inactive (disabled on boot)
contrail-named: inactive (disabled on boot)
contrail-dns: inactive (disabled on boot)
contrail-
== Contrail Config ==
contrail-api: inactive (disabled on boot)
contrail-schema: inactive (disabled on boot)
contrail-
contrail-
contrail-
== Contrail Config Database==
contrail-database: inactive (disabled on boot)
== Contrail Web UI ==
contrail-webui: inactive (disabled on boot)
contrail-
== Contrail Support Services ==
zookeeper: inactive
rabbitmq-server: inactive (disabled on boot)
root@nodem5:
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_
Oct 06 17:29:29 nodem5 systemd[1]: contrail-
Oct 06 17:29:29 nodem5 systemd[1]: Failed to start Contrail controller configuration.
Oct 06 17:29:31 nodem5 systemd[1]: contrail-
Oct 06 17:29:31 nodem5 systemd[1]: contrail-
root@nodem5:/#
description: | updated |
information type: | Proprietary → Public |
tags: | added: blocker feature |
metadata_ssl_enable needs to be set to true in json. Based on this Nova.conf and agent.conf are updated with metadata ssl encryption parameters.
When I set this parameter, internal ansible fails to validate the schema. So ansible launches the containers, but due to schema validation failure by internal ansible none of the services are launced