[centos65-icehouse-R1.10-#30] ping to metadata is failing

Moving bug from bugzilla to launchpad

Mahesh Loni 2014-03-28 02:49:14 PDT
One of the VM metadata ip is not pinging in mutinode centos setup:

setup details :
env.roledefs = {
    'all': [host1, host2, host3, host4, host5],
    'cfgm': [host1,host2,host3],
    'openstack': [host2],
    'control': [host2, host3],
    'compute': [host4, host5],
    'collector': [host1,host2,host3],
    'webui': [host1],
    'database': [host1,host2],
    'build': [host_build],
}

env.hostnames = {
    'all': [ 'nodea12', 'nodea13', 'nodea14', 'nodea17','nodeg11']
}

VM (vmc2) metadata ip is not pinging and its compute host is nodea17
default-domain:admin:vnet2
77a083c1-dc69-4070-beed-da479abfb9c5
vmc2:14.1.1.1
02:9b:d9:1f:ed:75
Enable
mdata_ip_addr
169.254.0.3
Comment 1 Praveen K V 2014-04-10 00:29:23 PDT
As per initial analysis, ping was attempted to a VSRX VM. VSRX does not respond to ping by default.

Please double check and move back the PR if destination was not VSRX VM.
Comment 2 Praveen K V 2014-04-10 02:16:35 PDT
Vrouter responds to ARP request for link-local IP of a VM.

In the test case, the ARP request from host-os was done before the link-local route was added to kernel. As a result, ARP request was sent on fabric network and was replied by all vrouters on the fabric. The ARP response is received by both vrouter and host-os.

vrouter accepts the ARP response and adds a /32 route with ARP-NH.

Subsequent route add for link-local route is overridden by ARP route since it has higher preference.

Proposed fix:
1. vrouter should not respond to ARP request for link-local IP for VMs
2. Path added for for link-local route should have higher preference than ARP route