route target lost on adding of Contrail nodes

Bug #1608962 reported by Illia Polliul
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Juniper Openstack
Status tracked in Trunk
R3.1
Won't Fix
Medium
Sachin Bansal
Trunk
Incomplete
Medium
Sachin Bansal

Bug Description

We deployed env with one Contrail node and after that added 2 more Contrail nodes.
After addition of Contrail nodes, route target for our floating network stopped to be advertised to router.
As a result routes were not leaking into public table.

Here is how we provision route target:

/bin/sh -c python /usr/share/contrail-utils/add_route_target.py \
--routing_instance_name default-domain:admin:admin_floating_net:admin_floating_net \
--route_target_number 10000 --router_asn 64512 \
--api_server_ip 10.109.4.2 \
--api_server_port 8082 \
--admin_user 'neutron’ \
--admin_tenant_name 'services’ \
--admin_password 'g1qQiMBDQDzQbMCrg9WWcN9m' && touch /etc/contrail/prov_route_target-DONE’

This data was present in Contrail WebUI, but effectively it wasn’t applied. After we removed route target and added it back - everything started to work fine.
All Contrail services were reporting as “green” in Contrail WebUI. Contrail version is 3.0.2.1-4

Tags: config
Illia Polliul (ipolliul)
affects: fuel-plugin-contrail → juniperopenstack
Jeba Paulaiyan (jebap)
Changed in juniperopenstack:
importance: Undecided → High
tags: added: contrail-control
Nischal Sheth (nsheth)
tags: added: config
removed: contrail-control
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.