Updating allowed address pair may affect bound ports
Bug #1730598 reported by
Oleg Bondarev
This bug affects 2 people
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Mirantis OpenStack |
Fix Released
|
High
|
MOS Maintenance | ||
Bug Description
MOS 9.2, no DVR, VxLAN/L2POP
Steps to reproduce:
- have 2 VMs on different compute nodes
- VM1 has floating IP attached
- update port of VM2, add allowed address pair with an IP of VM1
- VM1 port gets updated with HOST of VM2 port and
binding:profile {"original_owner": "compute:None"}
- connectivity issues of VM1
This was fixed upstream in master later as a side effect with patch
https:/
| no longer affects: | mos |
| Changed in mos: | |
| milestone: | none → 9.2-mu-5 |
| assignee: | nobody → MOS Maintenance (mos-maintenance) |
| importance: | Undecided → High |
| status: | New → Confirmed |
| no longer affects: | mos/9.x |
Revision history for this message
| Oleg Bondarev (obondarev) wrote | #1 |
| Changed in mos: | |
| status: | Confirmed → Fix Committed |
Revision history for this message
| Vladimir Jigulin (vjigulin) wrote | #2 |
| Changed in mos: | |
| status: | Fix Committed → Fix Released |
Revision history for this message
| Fuel Devops McRobotson (fuel-devops-robot) wrote Fix proposed to openstack/neutron (mcp/1.0/mitaka) | #3 |
To post a comment you must log in.
Fixed with https:/