agent: FIP not set on a VIP port

[Senthilnathan Murugappan]

Debugged with Tapan, From the xmpptrace it seems agent had downloaded both VMI and FIP and also their links from the active controller.

We have dumped the gcore and traces of both agent and control-node at 10.84.22.18:~/fip/

Looks like if the object and link were downloaded out of sequence we dont update the FIP on VMI
From the below trace, it seems the link update was received before fip object update was received.

Relevant xmpp trace:
2016-02-10 04:40:42.694 AgentXmppMessage: Received xmpp message from: 10.84.25.28 Port 5269 Size: 594 Packet: <?xml version="1.0"?> <iq type="set" <email address hidden>" to="default-global-system-config:b2s18/config"> <config> <update> <link> <node type="floating-ip"> <name>default-domain:admin:fip-vn:floating-ip-pool:fbee4f9f-b3c9-4efa-820e-764ce7d8a0b8</name> </node> <node type="virtual-machine-interface"> <name>default-domain:TestProjectec7d77:default-domain__TestProjectec7d77__d08b615b-86b2-4a8e-9b20-13089cab5d91__1__right__1</name> </node> <metadata type="floating-ip-virtual-machine-interface" /> </link> </update> </config> </iq> $ controller/src/vnsw/agent/controller/controller_init.cc 839
2016-02-10 04:40:42.694 AgentXmppMessage: Received xmpp message from: 10.84.25.28 Port 5269 Size: 1268 Packet: <?xml version="1.0"?> <iq type="set" <email address hidden>" to="default-global-system-config:b2s18/config"> <config> <update> <node type="floating-ip"> <name>default-domain:admin:fip-vn:floating-ip-pool:fbee4f9f-b3c9-4efa-820e-764ce7d8a0b8</name> <floating-ip-address>10.1.1.15</floating-ip-address> <floating-ip-fixed-ip-address>66.136.215.6</floating-ip-fixed-ip-address> <id-perms> <permissions> <owner>neutron</owner> <owner-access>7</owner-access> <group>admin</group> <group-access>7</group-access> <other-access>7</other-access> </permissions> <uuid> <uuid-mslong>18153534695311757050</uuid-mslong> <uuid-lslong>9371557947283906744</uuid-lslong> </uuid> <enable>true</enable> <created>2016-02-10T12:40:42</created> <last-modified>2016-02-10T12:40:42</last-modified> <description></description> <user-visible>true</user-visible> <creator></creator> </id-perms> <perms2> <owner>2d92c8052f4d4c5498f773ec989bff74</owner> <owner-access>7</owner-access> <global-access>0</global-access> </perms2> <display-name>fbee4f9f-b3c9-4efa-820e-764ce7d8a0b8</display-name> </node> </update> </config> </iq> $ controller/src/vnsw/agent/controller/controller_init.cc 839
2016-02-10 04:40:42.695 AgentXmppMessage: Received xmpp message from: 10.84.25.28 Port 5269 Size: 1081 Packet: <?xml version="1.0"?> <iq type="set" <email address hidden>" to="default-global-system-config:b2s18/config"> <config> <update> <node type="floating-ip-pool"> <name>default-domain:admin:fip-vn:floating-ip-pool</name> <id-perms> <permissions> <owner>neutron</owner> <owner-access>7</owner-access> <group>admin</group> <group-access>7</group-access> <other-access>7</other-access> </permissions> <uuid> <uuid-mslong>2884075085269454198</uuid-mslong> <uuid-lslong>13177331620828055294</uuid-lslong> </uuid> <enable>true</enable> <created>2016-02-09T22:30:41</created> <last-modified>2016-02-09T22:30:41</last-modified> <description></description> <user-visible>true</user-visible> <creator></creator> </id-perms> <perms2> <owner>2d92c8052f4d4c5498f773ec989bff74</owner> <owner-access>7</owner-access> <global-access>0</global-access> </perms2> <display-name>floating-ip-pool</display-name> </node> </update> </config> </iq> $ controller/src/vnsw/agent/controller/controller_init.cc 839
2016-02-10 04:40:42.695 AgentXmppMessage: Received xmpp message from: 10.84.25.28 Port 5269 Size: 503 Packet: <?xml version="1.0"?> <iq type="set" <email address hidden>" to="default-global-system-config:b2s18/config"> <config> <update> <link> <node type="floating-ip-pool"> <name>default-domain:admin:fip-vn:floating-ip-pool</name> </node> <node type="floating-ip"> <name>default-domain:admin:fip-vn:floating-ip-pool:fbee4f9f-b3c9-4efa-820e-764ce7d8a0b8</name> </node> <metadata type="floating-ip-pool-floating-ip" /> </link> </update> </config> </iq> $ controller/src/vnsw/agent/controller/controller_init.cc 839

Thanks,
Senthil

From: Tapan Karwa
Sent: Wednesday, February 10, 2016 1:21 PM
To: Senthilnathan Murugappan
Cc: Hari Prasad Killi; Ashish Ranjan; Harshad Nakil
Subject: Re: FIP not set for certain ports

That count is not a problem.
Why don’t you stop by?

On Feb 10, 2016, at 12:40 PM, Senthilnathan Murugappan <email address hidden> wrote:

Hi Hari, Tapan,

Observed that FIP wasn’t set for a particular port. From sandesh trace on agent observed the below however the active controller b5s28 has the configs.

2016-02-10 04:40:42.695 IFMapAgentTrace: seq = 1 event = floating-ip:default-domain:admin:fip-vn:floating-ip-pool:fbee4f9f-b3c9-4efa-820e-764ce7d8a0b8 not present for link to virtual-machine-interface:default-domain:TestProjectec7d77:default-domain__TestProjectec7d77__d08b615b-86b2-4a8e-9b20-13089cab5d91__1__right__1 file = controller/src/ifmap/ifmap_agent_table.cc line = 404

Also http://10.84.25.28:8083/Snh_IFMapXmppClientInfoShowReq? for b2s18 (compute host) shows a message been blocked.

Thanks,
Senthil

[OpenContrail Admin (ci-admin-f)]

Review in progress for https://review.opencontrail.org/17312
Submitter: Divakar Dharanalakota (<email address hidden>)

[OpenContrail Admin (ci-admin-f)]

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

commit 528906c930f2ce8a535b46cfe5b4e719e98420a9
Author: Divakar <email address hidden>
Date: Wed Feb 17 15:22:01 2016 +0530

Correct the metadata string of fip-pool to vn

The metadata mentioned in xsd for the link between floating-ip-pool to
VN is "virtual-network-floating-ip-pool" and Agent is adding a rule
in dependency manager for VMI as "floating-ip-pool-virtual-network".
This is resulting in no InterestedEvent in dependency tracker if the
link added between VN-FIP is the last link in that VMI.

As a fix, metadata is corrected in Agent.

Change-Id: I484099d8c843493cfcdb618a3165819f9eab5d08
closes-bug: #1544788

[OpenContrail Admin (ci-admin-f)]

Review in progress for https://review.opencontrail.org/17424
Submitter: Vinay Vithal Mahuli (<email address hidden>)

[OpenContrail Admin (ci-admin-f)]

Reviewed: https://review.opencontrail.org/17424
Committed: http://github.org/Juniper/contrail-controller/commit/a6be817f369ca6f2e30f2c3a39079e8a9133e5e9
Submitter: Zuul
Branch: R3.0

commit a6be817f369ca6f2e30f2c3a39079e8a9133e5e9
Author: Divakar <email address hidden>
Date: Wed Feb 17 15:22:01 2016 +0530

Correct the metadata string of fip-pool to vn

The metadata mentioned in xsd for the link between floating-ip-pool to
VN is "virtual-network-floating-ip-pool" and Agent is adding a rule
in dependency manager for VMI as "floating-ip-pool-virtual-network".
This is resulting in no InterestedEvent in dependency tracker if the
link added between VN-FIP is the last link in that VMI.

As a fix, metadata is corrected in Agent.

Change-Id: I484099d8c843493cfcdb618a3165819f9eab5d08
closes-bug: #1544788

Handle vxlan change for local_vm peer in l2 flood.

Change-Id: I3eb43c9541eec6ef3d343a8aa041b527033c24fe
Closes-bug: 1529665

Add ShowRouteAggregateSummaryReq introspect command

Change-Id: Ib633b018798e19c7fc73f4bebaef10283aef1a89
Related-bug: 1500698

database-purge request fails if analytics-api starts before cassandra

analytics-api creates cql session only on creation of AnalyticsDb
object. Therefore, if analytics-api starts before cassandra becomes
active, then database-purge request fails.

This patch ensures that the cql session is created upon purge request if
cql session is None.

Change-Id: Ic38d82cd1d614cd80af917ff205c3a63b95d6b92
Closes-Bug: #1546435

LBaaS scheduler should not use hardcoded tenant name

This fix removes the hardcoded 'admin' tenant name from
lbaas scheduler and reads the tenant from config.
It also fixes the default admin_tenant_name in svc_monitor.py
to 'admin'.
Closes-Bug: #1543296

Change-Id: If5e558e27ef6fd81d81cf56a317f39dbac2854ce

Fix error message

The VM uuid should be shown instead of the VN uuid

Change-Id: I56a65f5aabbc441139784e672babcf5e7508b880
Closes-Bug: #1546107

Adding UVE information for Health Check

Virtual Machine Interface UVE will also carry additional
information on the HealthCheck instances running on it,
its state and running status

Closes-Bug: 1546390
Change-Id: Ib6f2dac3e80544852359b8e7633343011b9f7a4e

Agent changes to accept port add requests without IP address.

This is done for both REST and thrift interface. Also add a flag to Flow info maintained
by FlowStatsCollector to indicate whether a delete was enqueued for that flow or not.

Change-Id: Ibe1cd81bcd71d42919995860e846383740bdfcdc
Closes-Bug: #1546939