R.3.1 build 33 : zookeeper ip not correct in analytics conf files
Affects | Status | Importance | Assigned to | Milestone | ||
---|---|---|---|---|---|---|
Juniper Openstack | Status tracked in Trunk | |||||
R3.0 |
Fix Committed
|
Critical
|
Ignatious Johnson Christopher | |||
R3.1 |
Fix Committed
|
Critical
|
Ignatious Johnson Christopher | |||
Trunk |
Fix Committed
|
Critical
|
Ignatious Johnson Christopher |
Bug Description
Most of the scripts in our sanity failed due to this issue.
Zookeeper seems to have moved to config node from db node through the below commit:
https:/
Analytics conf files (contrail-
In contrail-
zk_server_
Config Nodes : [u'nodei13-vm2']
Control Nodes : [u'nodei13-vm2', u'nodei14-vm2']
Compute Nodes : [u'nodea12', u'nodea15', u'nodea17']
Openstack Node : [u'nodek7-vm2']
WebUI Node : nodei13-vm2
Analytics Nodes : [u'nodei13-vm2']
root@nodei13-vm2:~# contrail-status
== Contrail Control ==
supervisor-control: active
contrail-control active
contrail-
contrail-dns active
contrail-named active
== Contrail Analytics ==
supervisor-
contrail-alarm-gen initializing (Zookeeper:
contrail-
contrail-
contrail-collector active
contrail-
contrail-
contrail-topology initializing (Zookeeper:
== Contrail Config ==
supervisor-config: active
contrail-api:0 active
contrail-
contrail-
contrail-
contrail-schema active
contrail-
ifmap active
== Contrail Web UI ==
supervisor-webui: active
contrail-webui active
contrail-
== Contrail Support Services ==
supervisor-
unix://
Changed in juniperopenstack: | |
importance: | Undecided → Critical |
milestone: | none → r3.2.0.0-fcs |
By any chance, did you use old fab to provision this setup?