[OVSDB-215] East-west traffic (with different network)does not work after a compute node is unstacked and re-stacked Created: 06/Oct/15 Updated: 29/May/18 Resolved: 15/Mar/16 |
|
| Status: | Resolved |
| Project: | ovsdb |
| Component/s: | openstack.net-virt |
| Affects Version/s: | unspecified |
| Fix Version/s: | None |
| Type: | Bug | ||
| Reporter: | Vasanthan Balasubramaniyan | Assignee: | Josh Hershberg |
| Resolution: | Duplicate | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
Operating System: All |
||
| Issue Links: |
|
||||||||
| External issue ID: | 4417 | ||||||||
| Priority: | High | ||||||||
| Description |
|
Build#: Lithium-SR1 Build local.conf snip Openstack setup Problem: Step to Recreate: 5.Disassociated floating IP,Deleted all VM's spwaned on compute node-2 and un-stacked 6.Restacked and provisioned new VM(s) with private ip on 2.1.1.x network and associated the floating IP address. Try following test: 3rd Test needs to passed via Private IP of VM as well.Since RouterGateway Interface contains 1.1.1.x Network. Workaround: Associated defect #4408,4346 |
| Comments |
| Comment by Vasanthan Balasubramaniyan [ 01/Feb/16 ] |
|
On Bery-RC1 Build,Openstack-Kilo While re-stack the compute node and create new VM's on existing network and associate the floating IP address,Unable to communicate via private IP's.However its managed to communicated via Floating IP to other compute node VM's floating IP address. Until hard-reboot of existing VM's(with existing network),VM cannot communicate with each-other with same private network IP's (spawn across different compute node). Hence this defect visible,with workaround as "reboot of existing VM" |