Comment 5 for bug 1489198

Revision history for this message
Anna Babich (ababich) wrote :

VERSION:
  feature_groups:
    - mirantis
  production: "docker"
  release: "7.0"
  openstack_version: "2015.1.0-7.0"
  api: "1.0"
  build_number: "288"
  build_id: "288"
  nailgun_sha: "93477f9b42c5a5e0506248659f40bebc9ac23943"
  python-fuelclient_sha: "1ce8ecd8beb640f2f62f73435f4e18d1469979ac"
  fuel-agent_sha: "082a47bf014002e515001be05f99040437281a2d"
  fuel-nailgun-agent_sha: "d7027952870a35db8dc52f185bb1158cdd3d1ebd"
  astute_sha: "a717657232721a7fafc67ff5e1c696c9dbeb0b95"
  fuel-library_sha: "121016a09b0e889994118aa3ea42fa67eabb8f25"
  fuel-ostf_sha: "1f08e6e71021179b9881a824d9c999957fcc7045"
  fuelmain_sha: "6b83d6a6a75bf7bca3177fcf63b2eebbf1ad0a85"

Verified on cluster: neutron+vxlan, 3 controllers, 2 computes

Steps to reproduce
1. Create net01: net01__subnet, 192.168.1.0/24, attach it to router04
2. Create vm1 and vm2 in net01 on different computes
3. Go to vm1's console and send pings to vm2
4. Go to vm2's console and send pings to 8.8.8.8
5. Go to compute's console where vm2 will be live-migrated to, and run tcpdump:
tcpdump -i br-mesh > rarp.log
6. Go to controller and initiate live migration for vm2:
nova live-migration --block-migrate vm2 node-2.domain.tld
7. Check that vm2 is hosted on a new compute now and grep rarp.log for Reverse ARP packets:
cat rarp.log | grep 'ARP, Reverse'

The bug was reproduced on ISO #259: about 3 packets were lost during migration and there were no RARP packets in rarp.log
It was rechecked on a current environment and the result is: http://paste.openstack.org/show/467698/