Activity log for bug #1623791

Date Who What changed Old value New value Message
2016-09-15 05:41:26 Ankit Jain bug added bug
2016-09-15 05:41:53 Ankit Jain nominated for series juniperopenstack/r3.1
2016-09-15 05:41:53 Ankit Jain bug task added juniperopenstack/r3.1
2016-09-15 05:42:06 Ankit Jain juniperopenstack/r3.1: milestone r3.1.1.0
2016-09-15 05:42:23 Ankit Jain juniperopenstack/r3.1: assignee Ignatious Johnson Christopher (ijohnson-x)
2016-09-15 05:42:54 Ankit Jain juniperopenstack/r3.1: importance Undecided Critical
2016-09-16 01:35:18 Jeba Paulaiyan juniperopenstack: importance Undecided Critical
2016-09-16 01:35:22 Jeba Paulaiyan juniperopenstack: milestone r3.2.0.0-fcs
2016-09-16 18:57:20 OpenContrail Admin nominated for series juniperopenstack/trunk
2016-09-16 18:57:20 OpenContrail Admin bug task added juniperopenstack/trunk
2016-09-16 18:57:20 OpenContrail Admin bug task added juniperopenstack/trunk
2016-09-16 19:00:47 OpenContrail Admin juniperopenstack/r3.1: status New In Progress
2016-09-16 19:00:53 OpenContrail Admin nominated for series juniperopenstack/r3.0
2016-09-16 19:00:53 OpenContrail Admin bug task added juniperopenstack/r3.0
2016-09-16 19:00:53 OpenContrail Admin bug task added juniperopenstack/r3.0
2016-09-16 19:24:20 Ankit Jain 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://bugs.launchpad.net/juniperopenstack/+bug/1619803 Analytics conf files are not updated as per this change made. Alalytics services still trying to connect to zookeeper believing it to be on db node. contrail-analytics-api.conf : zk_server_ip=10.204.217.179:2181 <- it should have been 10.204.217.172:2181 as zookeeper running on nodei13-vm2 not nodei14-vm2 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-control-nodemgr active contrail-dns active contrail-named active == Contrail Analytics == supervisor-analytics: active contrail-alarm-gen initializing (Zookeeper:Zookeeper[Connection time-out] connection down) contrail-analytics-api initializing (UvePartitions:UVE-Aggregation[Partitions:0] connection down) contrail-analytics-nodemgr active contrail-collector active contrail-query-engine active contrail-snmp-collector initializing (Zookeeper:Zookeeper[Connection time-out] connection down) contrail-topology initializing (Zookeeper:Zookeeper[Connection time-out] connection down) == Contrail Config == supervisor-config: active contrail-api:0 active contrail-config-nodemgr active contrail-device-manager active contrail-discovery:0 active contrail-schema active contrail-svc-monitor active ifmap active == Contrail Web UI == supervisor-webui: active contrail-webui active contrail-webui-middleware active == Contrail Support Services == supervisor-support-service: inactive unix:///var/run/supervisord_support_service.sockno 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://bugs.launchpad.net/juniperopenstack/+bug/1619803 Analytics conf files (contrail-alarm-gen.conf, contrail-topology.conf and contrail-snmp-collector.conf) are not updated as per this change made. Alalytics services still trying to connect to zookeeper believing it to be on db node. In contrail-alarm-gen.conf, contrail-topology.conf and contrail-snmp-collector.conf: zk_server_ip=10.204.217.179:2181 <- it should have been 10.204.217.172:2181 as zookeeper running on nodei13-vm2 not nodei14-vm2 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-control-nodemgr active contrail-dns active contrail-named active == Contrail Analytics == supervisor-analytics: active contrail-alarm-gen initializing (Zookeeper:Zookeeper[Connection time-out] connection down) contrail-analytics-api initializing (UvePartitions:UVE-Aggregation[Partitions:0] connection down) contrail-analytics-nodemgr active contrail-collector active contrail-query-engine active contrail-snmp-collector initializing (Zookeeper:Zookeeper[Connection time-out] connection down) contrail-topology initializing (Zookeeper:Zookeeper[Connection time-out] connection down) == Contrail Config == supervisor-config: active contrail-api:0 active contrail-config-nodemgr active contrail-device-manager active contrail-discovery:0 active contrail-schema active contrail-svc-monitor active ifmap active == Contrail Web UI == supervisor-webui: active contrail-webui active contrail-webui-middleware active == Contrail Support Services == supervisor-support-service: inactive unix:///var/run/supervisord_support_service.sockno
2016-09-17 23:12:58 OpenContrail Admin juniperopenstack/trunk: status In Progress Fix Committed
2016-09-17 23:56:45 OpenContrail Admin juniperopenstack/r3.1: status In Progress Fix Committed
2016-09-19 06:34:36 OpenContrail Admin juniperopenstack/r3.0: status In Progress Fix Committed
2016-09-19 06:34:38 OpenContrail Admin juniperopenstack/r3.0: milestone r3.0.3.0