This looks like a provisioning issue and there were multiple cores created because of that.
in contrail-collector.conf, we can see:
[CONFIGDB]
# AMQP related configs
rabbitmq_server_list = 10.204.216.105 :5672 10.204.216.106:5672 10.204.216.107:5672
As can be see, there is a space between 10.204.216.105 and :5672, which is causing the collector to core.
Same can be seen in contrail-control.conf as well and control is core-ing as well
Looking at /etc/contrailctl/analytics.conf, we see
external_rabbitmq_servers = 10.204.216.105 , 10.204.216.106, 10.204.216.107
This causes the mis-formed rabbitmq_server_list in daemon conf files.
The latest issue is not related to this bug, can you please file a new bug, and also provide the combined_json used for provisioning
This looks like a provisioning issue and there were multiple cores created because of that.
in contrail- collector. conf, we can see: server_ list = 10.204.216.105 :5672 10.204.216.106:5672 10.204.216.107:5672
[CONFIGDB]
# AMQP related configs
rabbitmq_
As can be see, there is a space between 10.204.216.105 and :5672, which is causing the collector to core. control. conf as well and control is core-ing as well
Same can be seen in contrail-
Looking at /etc/contrailct l/analytics. conf, we see rabbitmq_ servers = 10.204.216.105 , 10.204.216.106, 10.204.216.107 server_ list in daemon conf files.
external_
This causes the mis-formed rabbitmq_
The latest issue is not related to this bug, can you please file a new bug, and also provide the combined_json used for provisioning