← Back to team overview

yahoo-eng-team team mailing list archive

[Bug 1929998] Re: VXLAN interface cannot source from lo with multiple IPs

 

Reviewed:  https://review.opendev.org/c/openstack/neutron/+/793500
Committed: https://opendev.org/openstack/neutron/commit/4cd11f4dee494c5851318410c523dfcfbce4c824
Submitter: "Zuul (22348)"
Branch:    master

commit 4cd11f4dee494c5851318410c523dfcfbce4c824
Author: Anthony Timmins <atimmins@xxxxxxxxx>
Date:   Thu May 27 16:11:04 2021 -0400

    Use local and ip address to create vxlan interface
    
    Attempting to terminate a vxlan on the lo interface with
    multiple ip addresses fails. This seems to be because only
    the first ip address on the interface is used. If this address
    is invalid for vxlan creation (ie. 127.0.0.1), the vxlan
    interface will be created, but will not have a source ip
    address, and will therefore be non-functional. To remedy this
    issue, when L2population is used, we can set the local
    argument to the local_ip, thus ensuring the intended ip
    address is configured.
    
    Closes-Bug: 1929998
    Change-Id: I9c54a268fc4ef9705637556ecba161bd6523a047
    Signed-off-by: Anthony Timmins <atimmins@xxxxxxxxx>


** Changed in: neutron
       Status: In Progress => Fix Released

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

Title:
  VXLAN interface cannot source from lo with multiple IPs

Status in neutron:
  Fix Released

Bug description:
  Attempting to terminate a vxlan on the lo interface with
  multiple ip addresses fails. This seems to be because only
  the first ip address on the interface is used. If this address
  is invalid for vxlan creation (ie. 127.0.0.1), the vxlan
  interface will be created, but will not have a source ip
  address, and will therefore be non-functional. By setting and
  including the local argument during vxlan interface creation,
  we can ensure that the intended ip address is used.

  Linux version: Ubuntu 20.04.1 LTS
  Neutron version: neutron-21.0.0.0rc3.dev1

  Current behavior:

  #No source IP address is found on the vxlan interface

  1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
      link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
      inet 127.0.0.1/8 scope host lo
         valid_lft forever preferred_lft forever
      inet 10.1.1.1/32 scope global lo
         valid_lft forever preferred_lft forever
      inet6 ::1/128 scope host 
         valid_lft forever preferred_lft forever

  # ip a show dev vxlan-62
  <...>
  vxlan id 62 dev lo srcport 0 0 dstport 8472 ttl 32 ageing 300 udpcsum noudp6zerocsumtx noudp6zerocsumrx

  Expected behavior:

  #The source IP address is configured correctly

  1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
      link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
      inet 127.0.0.1/8 scope host lo
         valid_lft forever preferred_lft forever
      inet 10.1.1.1/32 scope global lo
         valid_lft forever preferred_lft forever
      inet6 ::1/128 scope host 
         valid_lft forever preferred_lft forever

  # ip a show dev vxlan-62
  <...>
  vxlan id 62 local 10.1.1.1 dev lo srcport 0 0 dstport 8472 ttl 32 ageing 300 udpcsum noudp6zerocsumtx noudp6zerocsumrx

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


References