| 2018-10-22 06:49:41 |
LIU Yulong |
bug |
|
|
added bug |
| 2018-10-22 06:49:57 |
LIU Yulong |
description |
Should not allow creating port_forwarding to a port which already has a binding floating IP for dvr routers.
ENV: devstack master
step to reproduce:
1. create dvr router with connected privated subnet and public gateway.
2. create VM to the private subnet
3. create floating IP B with port forwarding to the VM port
4. binding floating IP B to VM port
Then floating IP B with port forwarding will not work. This should be restricted by neutron. |
Should not allow creating port_forwarding to a port which already has a binding floating IP for dvr routers.
ENV: devstack master
step to reproduce:
1. create dvr router with connected privated subnet and public gateway.
2. create VM to the private subnet
3. binding floating IP B to VM port
4. create floating IP B with port forwarding to the VM port
Then floating IP B with port forwarding will not work. This should be restricted by neutron. |
|
| 2018-10-22 06:51:37 |
LIU Yulong |
description |
Should not allow creating port_forwarding to a port which already has a binding floating IP for dvr routers.
ENV: devstack master
step to reproduce:
1. create dvr router with connected privated subnet and public gateway.
2. create VM to the private subnet
3. binding floating IP B to VM port
4. create floating IP B with port forwarding to the VM port
Then floating IP B with port forwarding will not work. This should be restricted by neutron. |
Should not allow creating port_forwarding to a port which already has a binding floating IP for dvr routers.
ENV: devstack master
step to reproduce:
1. create dvr router with connected privated subnet and public gateway.
2. create VM to the private subnet
3. binding floating IP A to VM port
4. create floating IP B with port forwarding to the VM port
Then floating IP B with port forwarding will not work. This should be restricted by neutron. |
|
| 2018-10-23 00:23:58 |
Brian Haley |
neutron: importance |
Undecided |
Medium |
|
| 2018-10-23 00:24:01 |
Brian Haley |
bug |
|
|
added subscriber Brian Haley |
| 2018-10-23 14:53:31 |
Akihiro Motoki |
tags |
|
l3-ipam-dhcp |
|
| 2018-10-23 15:23:28 |
LIU Yulong |
description |
Should not allow creating port_forwarding to a port which already has a binding floating IP for dvr routers.
ENV: devstack master
step to reproduce:
1. create dvr router with connected privated subnet and public gateway.
2. create VM to the private subnet
3. binding floating IP A to VM port
4. create floating IP B with port forwarding to the VM port
Then floating IP B with port forwarding will not work. This should be restricted by neutron. |
Should not allow creating port_forwarding to a port which already has a binding floating IP for dvr routers.
ENV: devstack master
step to reproduce:
1. create one distributed router, and connected it to private subnet, and set public gateway.
2. create VM to the private subnet
3. binding floating IP A to VM port
4. create floating IP B with port forwarding to the VM port
Then floating IP B with port forwarding will not work. This should be restricted by neutron. |
|
| 2018-10-27 17:49:12 |
Armando Migliaccio |
neutron: status |
New |
Incomplete |
|
| 2018-10-31 09:38:10 |
OpenStack Infra |
neutron: status |
Incomplete |
In Progress |
|
| 2018-10-31 09:38:10 |
OpenStack Infra |
neutron: assignee |
|
LIU Yulong (dragon889) |
|
| 2018-11-21 10:15:59 |
OpenStack Infra |
neutron: status |
In Progress |
Fix Released |
|
| 2019-06-25 19:35:55 |
OpenStack Infra |
tags |
l3-ipam-dhcp |
in-stable-rocky l3-ipam-dhcp |
|
