[3.0-2699~juno]Service chain between two networks configured using Port-Tuple doesn't work until schema is restarted

[Ganesha HV]

1]. Topo
=======
    'cfgm': ['nodeg25', 'nodeg26', 'nodeg27'],
    'webui': [nodeg25],
    'openstack': [nodeg25],
    'control': ['nodeg26', 'nodeg27',],
    'collector': [nodeg25],
    'database': [nodeg25],
    'compute': ['nodek8', 'nodek9', 'nodek10']

2]. Steps to recreate
=================
The scripts are placed in nodeg25 under /root/API

a). Launch VNs using 'bash vns.sh'. This uses neutron commands.
b). Launch VMs using 'bash vms.sh'. This uses nova commands.
c). Launch the SVM using 'bash svm.sh'. This uses nova commands as well to boot a VM with multiple NICs.
d). Run 'python st.py' to create the ST. Change the network-name and IDs wherever needed.
e). Run 'python si.py' to create the SI. Use the UUID of the ST previuosly created.
f). Run 'python port_tuple.py' to create the port_tuple. Use the port IDs of the SVM previously created and the UUID os the SI.
g). Run 'python pol.py' to create the service-chain, using the IDs of the neutron nets created previously.

Observed that the service-chain is not created and no VRFs are created.

The following log is observed in the contrail-schema.log :

01/26/2016 01:49:08 AM [contrail-schema]: service chain %s: Left interface not found for default-domain:admin:pt_si_ganesha:pt_ganesha
01/26/2016 01:49:08 AM [contrail-schema]: service chain %s: Left interface not found for default-domain:admin:pt_si_ganesha:pt_ganesha

After restarting schema, the chain begins to work.

Sachin has taken a look at the issue.

[OpenContrail Admin (ci-admin-f)]

Review in progress for https://review.opencontrail.org/16536
Submitter: Sachin Bansal (<email address hidden>)

[OpenContrail Admin (ci-admin-f)]

Reviewed: https://review.opencontrail.org/16536
Committed: http://github.org/Juniper/contrail-controller/commit/bdd1190a661cff107cd0252c95878a4b1dd01a46
Submitter: Zuul
Branch: master

commit bdd1190a661cff107cd0252c95878a4b1dd01a46
Author: Sachin Bansal <email address hidden>
Date: Tue Jan 26 14:46:38 2016 -0800

Update port-tuple to vmi link when port tuple is updated

When port tuple is updated, we were not updating the link to
vmi in our internal cache. As a result, subsequent walks of
dependency tracker don't work correctly.

In addition, at few places, reaction map was not correctly
set up to walk port tuples.

Also fixed a bunch of introspect related issues that I found
during debugging.

Change-Id: Iccade0e15b1f5939e96961e9266aec8cfab17ebc
Closes-Bug: 1537896