[regression] fab setup_nfs_livem_global timed out pinging active livemnfs vm

[wenqing liang]

R2.1-6 build.

fab setup_nfs_livem_global timed out as ping to active livemnfs vm on compute failed.

2015-01-17 21:42:00:075430: [root@10.87.129.173] out: [10.87.129.173] out: [localhost] local: source /etc/contrail/openstackrc && cinder list | grep livemnfsvol | grep available | wc -l^M
2015-01-17 21:42:05:086445: [root@10.87.129.173] out: [10.87.129.173] out: [localhost] local: source /etc/contrail/openstackrc && nova list |grep livemnfs | awk '{print $2}'^M
2015-01-17 21:42:05:651245: [root@10.87.129.173] out: [10.87.129.173] out: [localhost] local: source /etc/contrail/openstackrc && cinder list |grep livemnfsvol | awk '{print $2}'^M
2015-01-17 21:42:07:354439: [root@10.87.129.173] out: [10.87.129.173] out: [localhost] local: source /etc/contrail/openstackrc && cinder list | grep livemnfsvol | grep d20bde26-89fd-4c13-87e4-29bf5dde8371 | wc -l^M
2015-01-17 21:42:07:955709: [root@10.87.129.173] out: [10.87.129.173] out: [localhost] local: source /etc/contrail/openstackrc && nova volume-attach d20bde26-89fd-4c13-87e4-29bf5dde8371 c916ddc9-093b-437f-85b2-6cea55d65a1a /dev/vdb^M
2015-01-17 21:42:08:472269: [root@10.87.129.173] out: [10.87.129.173] out: Waiting for volume to be attached to VM^M
2015-01-17 21:42:10:591294: [root@10.87.129.173] out: [10.87.129.173] out: [localhost] local: source /etc/contrail/openstackrc && cinder list | grep livemnfsvol | grep d20bde26-89fd-4c13-87e4-29bf5dde8371 | wc -l^M
2015-01-17 21:42:15:600350: [root@10.87.129.173] out: [10.87.129.173] out: [localhost] local: ping -c 1 192.168.96.3 | grep " 0% packet loss" |wc -l^M
2015-01-17 21:42:16:133092: [root@10.87.129.173] out: [10.87.129.173] out: Waiting for VM to come up^M
2015-01-17 21:42:26:150215: [root@10.87.129.173] out: [10.87.129.173] out: [localhost] local: ping -c 1 192.168.96.3 | grep " 0% packet loss" |wc -l^M
2015-01-17 21:42:36:169007: [root@10.87.129.173] out: [10.87.129.173] out: Waiting for VM to come up^M

nova list^M
+--------------------------------------+----------+--------+------------+-------------+-----------------------+^M
| ID | Name | Status | Task State | Power State | Networks |^M
+--------------------------------------+----------+--------+------------+-------------+-----------------------+^M
| d20bde26-89fd-4c13-87e4-29bf5dde8371 | livemnfs | ACTIVE | - | Running | livemnfs=192.168.96.3 |^M
+--------------------------------------+----------+--------+------------+-------------+-----------------------+^M
^[]0;root@cmbu-vse2100-1:
 ~^G
Sat Jan 17 22:36:51 2015
CMD:cinder list --display-name=
Sat Jan 17 22:36:52 2015
~# cinder list --display-name=^M
+--------------------------------------+--------+--------------+------+----------------+----------+--------------------------------------+^M
| ID | Status | Display Name | Size | Volume Type | Bootable | Attached to |^M
+--------------------------------------+--------+--------------+------+----------------+----------+--------------------------------------+^M
| c916ddc9-093b-437f-85b2-6cea55d65a1a | in-use | livemnfsvol | 152 | ocs-block-disk | false | d20bde26-89fd-4c13-87e4-29bf5dde8371 |^M
+--------------------------------------+--------+--------------+------+----------------+----------+--------------------------------------+^M
^[]0;root@cmbu-vse2100-1:

[Jeya ganesh babu J (jjeya)]

Issue seems to be in the vgw

From: Naveen N <email address hidden>
Date: Monday, January 26, 2015 at 9:17 PM
To: Prasad Miriyala <email address hidden>
Cc: Praveen K V <email address hidden>, Hari Prasad Killi <email address hidden>, Jeya Ganesh Babu Jegatheesan <email address hidden>
Subject: Re: Setup details for the vgw issue

There is a bug in agent, we were not adding VGW mac address route to layer-2 table,
ad hence packet are getting dropped.

Regards
Naveen N

[Jeya ganesh babu J (jjeya)]

Still seeing the following issues -

1. The VM is accessible from the compute node where the VM is running, but its not accessible from other compute nodes via the vrouter interface (Its accessible when i add a route via the management interface).
2. The first ping packet is always lost.

[OpenContrail Admin (ci-admin-f)]

Reviewed: https://review.opencontrail.org/6881
Committed: http://github.org/Juniper/contrail-provisioning/commit/9deb21a8a8a61e851e489feab9f2e311adefdebd
Submitter: Zuul
Branch: R2.1

commit 9deb21a8a8a61e851e489feab9f2e311adefdebd
Author: Jeya ganesh babu J <email address hidden>
Date: Sun Feb 1 23:24:28 2015 -0800

Live migration provision changes for vgw changes

Closes-Bug: #1412286
Issue: Change in the vgw in 2.1 needs change in the route added
in the compute nodes. In pre 2.1 release, the compute nodes
were added with routes pointing to dev vhost0. From 2.1,
the routes has to be added with gateway option pointing to
the interface address.
Fix: Modified the provision script for the route change.
Also fixed the vif mac address.

Change-Id: I40d68bd8901e824a7c6f924da2f963bad48bb873

[OpenContrail Admin (ci-admin-f)]

Reviewed: https://review.opencontrail.org/7739
Committed: http://github.org/Juniper/contrail-provisioning/commit/a235dbb658f16d1f7fc35befa95d8069b002f2f2
Submitter: Zuul
Branch: master

commit a235dbb658f16d1f7fc35befa95d8069b002f2f2
Author: Jeya ganesh babu  <email address hidden>
Date: Mon Feb 23 13:55:42 2015 -0800

Live migration provision changes for vgw changes

Closes-Bug: #1412286, #1424310
Issue: Change in the vgw in 2.1 needs change in the route added
in the compute nodes. In pre 2.1 release, the compute nodes
were added with routes pointing to dev vhost0. From 2.1,
the routes has to be added with gateway option pointing to
the interface address.
Vgw changes done in 2.1 causes the existing livemigration
config to fail during upgrade.
Fix: Modified the provision script for the route change.
Also fixed the vif mac address.
After an upgrade from earlier release to 2.1, the setup_nfs_livem
has to be run again. With the run, the configuration will be
modified to the correct one. Changes done in the vgw vif mac
address and the route on other compute nodes.

Change-Id: I615aca660c1f6eb617397ace3839196eea715d7c