← Back to team overview

yahoo-eng-team team mailing list archive

[Bug 1841741] Re: Port-Forwarding can't be set to different protocol in the same IP and Port

 

*** This bug is a duplicate of bug 1799155 ***
    https://bugs.launchpad.net/bugs/1799155

Hi, I marked this as duplicate of the original bug report #1799155.
Unfortunately as I see by policy it can't be backported as the fix you referenced (https://review.opendev.org/613549) contains db schema change.

** This bug has been marked a duplicate of bug 1799155
   [L3][port_forwarding] two different protocols can not have the same internal/external port number at the same time

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1841741

Title:
  Port-Forwarding can't be set to different protocol in the same IP and
  Port

Status in neutron:
  New

Bug description:
  In Rocky version, Port-Forwarding can't be set to different protocol
  in the same IP and Port.

  For example:

  Floating IP(IP:140.128.100.100, Port:100) mapping to Private IP(IP:
  10.0.0.1. Port: 100, Protocol: tcp and udp)

  I got these error messages

  {
      "NeutronError": {
          "message": "Bad port_forwarding request: A duplicate port forwarding entry with same attributes already exists, conflicting values are {'floatingip_id': u'cdbe8e24-f0dc-45c9-aec7-9609faf4234c', 'external_port': 1000}.",
          "type": "BadRequest",
          "detail": ""
      }
  }

  And, I found this bug has been solved and merged in Stein version.
  Commit: https://github.com/openstack/neutron/commit/4b7a070b3f1c66afc48d1290ec31c840e367d8ee#diff-02580f01f1bafd7855f5f78a84ce1d5d

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1841741/+subscriptions


References