contrail-ansible: configuration for analytics wrongly configures zookeeper of contrail-controller instead of contrail-analyticsdb

Bug #1773091 reported by Bernhard Koessler on 2018-05-24
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Juniper Openstack
Status tracked in Trunk
Fix Committed
Sundaresan Rajangam
Sundaresan Rajangam
Sundaresan Rajangam

Bug Description

zookeeper in contrail-analyticsdb container runs a separate cluster listening on port 2182 per default (as compared to 2181 on contrail-controller) as per

It is expected that analytics services connect to the zookeeper cluster running on analyticsdb. However, analytics services are configured with the same zookeeper list/port as the controller, e.g.:

where zk_servers_with_port is defined here derived from zk_server_list:

and zk_server_list is derived from config_server_list:

Bernhard Koessler (bkoessler) wrote :

Need fix for 4.1.

Abhay Joshi (abhayj) wrote :

2 Things:

1. Bug is applicable to 4.1.x only and not 5.x, hence marking 5.x instances as invalid.
2. Bug is for analytics team to look into.

Review in progress for
Submitter: Santosh Gupta (<email address hidden>)

Santosh Gupta (sangupta) wrote :

In R5.0 and trunk, analytics services already point to analyticsdb zookeeper instance. Hence no fix is needed.

Submitter: Zuul (<email address hidden>)
Branch: R4.1

commit efe898d787f73a93060bd651a9dde3796590ad79
Author: Santosh Gupta <email address hidden>
Date: Tue Jun 26 11:46:56 2018 -0700

Analytics services point to analyticsdb zookeeper

Provision analytics services to use analyticsdb zookeeper on port 2182

Change-Id: Iadbb79990be15f581298effcebd2dcfdda6cdb9a
Closes-Bug: #1773091

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers