yahoo-eng-team team mailing list archive

[OpenStack Infra <1577289@xxxxxxxxxxxxxxxxxx>]

Public bug reported:

https://review.openstack.org/267891
Dear bug triager. This bug was created since a commit was marked with DOCIMPACT.
Your project "openstack/neutron" is set up so that we directly report the documentation bugs against it. If this needs changing, the docimpact-group option needs to be added for the project. You can ask the OpenStack infra team (#openstack-infra on freenode) for help if you need to.

commit 4858cd7cb97354ae54f8e7d47aeaaddad714c9dd
Author: Dustin Lundquist <dustin@xxxxxxxxxxxx>
Date:   Mon Jul 6 13:53:46 2015 -0700

    Ensure floating IPs only use IPv4 addresses
    
    Description:
    Presently Neutron doesn't validate the address family of floating IP
    addresses or the internal addresses they are associated with. It merely
    associates the first IP of the floating IP's port with the first IP of
    the internal port, unless a specified fixed IP is specified. This can
    lead to incorrect or poorly defined behavior when IPv6 is present.
    
    The existing L3 agent implementation only manages IPv4 NAT rules. While
    IPv6 NAT and NAT protocol translation are possible, the existing
    implementation does not support these configurations.
    
    Presently a floating IP can be created on an IPv6 only external network
    or associated with an IPv6 fixed IP, but the L3 agent is unable to bind
    these configurations.
    
    Implementation:
    When creating and updating a floating IP, only consider IPv4 addresses
    on both the floating IPs port and the internal port he floating IP is
    associated with. Additionally disallow creating floating IPs on networks
    without any IPv4 subnets, since these floating IPs could not be
    allocated an IPv4 address.
    
    DocImpact
    APIImpact
    
    Co-Authored-By: Bradley Jones <jones.bradley@xxxxxx>
    Change-Id: I79b28a304b38ecdafc17eddc41213df1c24ec202
    Related-Bug: #1437855
    Closes-Bug: #1323766
    Closes-Bug: #1469322
    (cherry picked from commit 4cdc71e7d0e5220a5f12ee2dfea1ff3db045c041)

** Affects: neutron
     Importance: Undecided
         Status: New


** Tags: doc neutron

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

Title:
      Ensure floating IPs only use IPv4 addresses

Status in neutron:
  New

Bug description:
  https://review.openstack.org/267891
  Dear bug triager. This bug was created since a commit was marked with DOCIMPACT.
  Your project "openstack/neutron" is set up so that we directly report the documentation bugs against it. If this needs changing, the docimpact-group option needs to be added for the project. You can ask the OpenStack infra team (#openstack-infra on freenode) for help if you need to.

  commit 4858cd7cb97354ae54f8e7d47aeaaddad714c9dd
  Author: Dustin Lundquist <dustin@xxxxxxxxxxxx>
  Date:   Mon Jul 6 13:53:46 2015 -0700

      Ensure floating IPs only use IPv4 addresses
      
      Description:
      Presently Neutron doesn't validate the address family of floating IP
      addresses or the internal addresses they are associated with. It merely
      associates the first IP of the floating IP's port with the first IP of
      the internal port, unless a specified fixed IP is specified. This can
      lead to incorrect or poorly defined behavior when IPv6 is present.
      
      The existing L3 agent implementation only manages IPv4 NAT rules. While
      IPv6 NAT and NAT protocol translation are possible, the existing
      implementation does not support these configurations.
      
      Presently a floating IP can be created on an IPv6 only external network
      or associated with an IPv6 fixed IP, but the L3 agent is unable to bind
      these configurations.
      
      Implementation:
      When creating and updating a floating IP, only consider IPv4 addresses
      on both the floating IPs port and the internal port he floating IP is
      associated with. Additionally disallow creating floating IPs on networks
      without any IPv4 subnets, since these floating IPs could not be
      allocated an IPv4 address.
      
      DocImpact
      APIImpact
      
      Co-Authored-By: Bradley Jones <jones.bradley@xxxxxx>
      Change-Id: I79b28a304b38ecdafc17eddc41213df1c24ec202
      Related-Bug: #1437855
      Closes-Bug: #1323766
      Closes-Bug: #1469322
      (cherry picked from commit 4cdc71e7d0e5220a5f12ee2dfea1ff3db045c041)

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