Deleting and readding the same VIP results in a non-working VIP
Bug #1301165 reported by
Liping Mao
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
neutron |
Fix Released
|
Medium
|
Liping Mao |
Bug Description
Environment:
Openstack Version : Havana
OS : CentOS6.3
LBaaS Driver : haproxy
Reproduce Steps:
1. In loadbalance pool, add vip :100.100.100.100. This vip is on a provider network and will use external Physical Router.
2. Access 100.100.100.100, make sure it can work.
3. Delete vip.
4. Add vip 100.100.100.100 again.
We will find that we can't access 100.100.100.100 at the second time.
tags: | added: lbaas |
description: | updated |
Changed in neutron: | |
importance: | Undecided → Medium |
summary: |
- lbaas delete and re-add same vip will make the vip can't work + Deleting and readding the same VIP results in a non-working VIP |
Changed in neutron: | |
milestone: | none → juno-1 |
status: | Fix Committed → Fix Released |
Changed in neutron: | |
milestone: | juno-1 → 2014.2 |
To post a comment you must log in.
Route Cause:
When we access 100.100.100.100 at first time, there will be arp info in the External Router. And after we delete vip and create vip 100.100.100.100 again, the MAC change. But there still be ARP cache in external Router.
Solution: /bugzilla. redhat. com/show_ bug.cgi? id=963927
When we create the port, we need send gratuitous ARP to flash the ARP cache in External Router.
Our deploy is on CentOS6.3, there is the following Bug make arping can't work in netns, so I think we can just use ping gateway to reflash the ARP cache on External Router:
https:/