GitHub user remibergsma opened a pull request:
https://github.com/apache/cloudstack/pull/1163
Send arping to the gateway instead of our own address
We need to send an Unsolicited ARP to the gateway, instead of our own
address. We now encounter problems when people deploy/destroy/deploy and get
the same public ip.
Packets arrive, but with incorrect / cached mac and are ignored by the
routervm kernel.
Run arping manually to update the arp-cache on the gateway and things start
to work.
Then we discovered the `arping` is actually done, but sent to its own
address. Therefore the gateway doesn't pick it up. We only saw this happening
when rapid deploy tools are used, like Terraform that do deploy/destroy/deploy
and might get the same ip but on a new router having a new mac.
```
2015-12-03 18:07:25,589 CsHelper.py execute:160 Executing: arping -c 1 -I
eth1 -A -U -s 192.168.23.8 192.168.23.1
```
The integration tests seem happy, although the full run is still ongoing:
```
=== TestName: test_01_create_redundant_VPC_2tiers_4VMs_4IPs_4PF_ACL |
Status : SUCCESS ===
```
Thanks @sspans for helping trouble shoot this. Ping @wilderrodrigues can
you review please?
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/remibergsma/cloudstack arping-to-gw
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/cloudstack/pull/1163.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #1163
----
commit 90e01c95a2db3d9b7c6586b2b228e0a9c5b9e415
Author: Remi Bergsma <[email protected]>
Date: 2015-12-03T17:15:31Z
CLOUDSTACK-9097 Make public ip work immediately
We need to send an Unsolicited ARP to the gateway, instead of our own
address. We now encounter problems when people deploy/destroy/deploy and get
the same public ip.
----
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---
