2.2-B64:Static Routes configured/deleted on Service Instances do not change the VRF table.
Affects | Status | Importance | Assigned to | Milestone | ||
---|---|---|---|---|---|---|
Juniper Openstack | Status tracked in Trunk | |||||
R2.20 |
Fix Committed
|
High
|
Rudra Rugge | |||
Trunk |
Fix Committed
|
High
|
Rudra Rugge |
Bug Description
The FRS version Contrail 2.2 Build 64 seems to have issues in updating the static route entries in the VRF table.
Here is the setup :
10.209.107.20 (cfgm/contrail)
10.209.107.21 ( compute1 )
10.209.107.22 ( compute2 )
Credentials: root/contrail
Topology here :
<<left-
Dynamically, add a static route on one of the interfaces on the service instance firewall.
For e.g), I edit the service instance and add a static route on right vrf of the firewall - 200.200.200.0/24
Post saving, if you check the routes under service-
This seems to be broken. Can you please check and provide a workaround. We have a PS working with a customer and is blocked due to this.
The only static route related I could find from launchpad was bug id 1466755 ( not sure whether this has anything to do with the problem being described ).
Greetings,
Sandeep.
Changed in juniperopenstack: | |
importance: | Undecided → High |
tags: | added: config service-chain |
Changed in juniperopenstack: | |
assignee: | nobody → Rudra Rugge (rudrarugge) |
information type: | Proprietary → Public |
Upon updating service instance static route list, interface route table
for the VMI is not updated with same data.
ServiceInstance snippet: network> default- domain: admin:left- network< /virtual- network> address> </ip-address> 1.1.1.0/ 24</prefix> hop></next- hop> hop-type> </next- hop-type>
<interface-list>
<virtual-
<ip-
<static-routes>
<route>
<prefix>
<next-
<next-
</route>
</static-routes>
</interface-list>
Interface route table corresponding to the same
<iq> route-table- routes /> admin</ owner> access> 7</owner- access> KeystoneService Admin</ group> access> 7</group- access> access> 7</other- access> mslong> 238022681667196 0413</uuid- mslong> lslong> 117717357885660 25470</ uuid-lslong> true</enable> 2015-07- 29T09:28: 47</created> modified> 2015-07- 29T09:28: 48</last- modified> </description> visible> true</user- visible> </creator> name>e353a74d- f78e-4bf8- 8640-9c909b18e2 0e left</display-name>
<interface-
<id-perms>
<permissions>
<owner>
<owner-
<group>
<group-
<other-
</permissions>
<uuid>
<uuid-
<uuid-
</uuid>
<enable>
<created>
<last-
<description>
<user-
<creator>
</id-perms>
<display-
</iq>
Looks like if SI is in active state, any config change on the static route doesn't seem to be updated in interface route table.