[L3][port_forwarding] two different protocols can not have the same internal/external port number at the same time
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
neutron |
Fix Released
|
Medium
|
LIU Yulong |
Bug Description
ENV: devstack master
Floating IP port_forwardings with different protocols can not have the same internal or external port number to the same vm_port. But we can have different application server, for instance TCP server and UDP server, listen to the same port at same time.
For instance, if you create a port_forwarding to a floating IP with the following input:
{"port_forwarding":
{
"internal_port_id": "3145b56c-
"internal_port": 22,
"protocol": "tcp",
"external_port": 22,
"internal_
}
}
And then add another port_forwarding with protocol to udp and internal port number 22 again:
{"port_forwarding":
{
"internal_port_id": "3145b56c-
"internal_port": 22,
"protocol": "udp",
"external_port": 2222,
"internal_
}
}
The neutron will return 40x error.
This is the key point, these unique constraints do not consider the protocol:
https:/
summary: |
- [l3][port_forwarding] tow different protocols can not have the same + [l3][port_forwarding] two different protocols can not have the same internal/external port number at the same time |
Changed in neutron: | |
status: | New → Confirmed |
importance: | Undecided → Medium |
summary: |
- [l3][port_forwarding] two different protocols can not have the same + [L3][port_forwarding] two different protocols can not have the same internal/external port number at the same time |
Fix proposed to branch: master /review. openstack. org/613549
Review: https:/