Uploaded image for project: 'OpenShift Bugs'
  1. OpenShift Bugs
  2. OCPBUGS-46401

[4.18] Virtual machines using primary UDN layer2 end up with IPv6 multipath gateway

XMLWordPrintable

    • Quality / Stability / Reliability
    • False
    • Hide

      None

      Show
      None
    • None
    • None
    • None
    • None
    • None
    • None
    • Done
    • Bug Fix
    • Hide
      * Before this update, Kubernetes VM with dynamic IPv6 configuration used primary user-defined network (UDN) layer2, which caused the default IPv6 gateway to be multipath. As a consequence, user traffic flowed incorrectly between nodes because of multiple default IPv6 gateways. With this release, the default IPv6 gateway is correct for dynamic VM configurations due to using the new Open Virtual Network (OVN) transit router topology. As a result, the default IPv6 gateway points to the correct node, which reduces inter-node traffic and improves network stability during node maintenance. (link:https://issues.redhat.com/browse/OCPBUGS-46401[OCPBUGS-46401])
      Show
      * Before this update, Kubernetes VM with dynamic IPv6 configuration used primary user-defined network (UDN) layer2, which caused the default IPv6 gateway to be multipath. As a consequence, user traffic flowed incorrectly between nodes because of multiple default IPv6 gateways. With this release, the default IPv6 gateway is correct for dynamic VM configurations due to using the new Open Virtual Network (OVN) transit router topology. As a result, the default IPv6 gateway points to the correct node, which reduces inter-node traffic and improves network stability during node maintenance. (link: https://issues.redhat.com/browse/OCPBUGS-46401 [ OCPBUGS-46401 ])
    • None
    • None
    • None
    • None

      Description of problem:

      When Virtual Machine using dynmiac ipv6 configuration is using primary UDN layer2 it ends up with multipath ipv6 default gw, since all the gateway routers from this topology are answering back the Router Solicitation.

      This has two main problems:

      • All the VM north/south traffic will flow inter node
      • If one of the node is down it will affect north/south traffic, this is very common after live migration done to repair or replace a node.

       

      Version-Release number of selected component (if applicable): 4.18

      How reproducible: Always

       

      Steps to Reproduce:

      1. Start a kubevirt virtual machine with dynamic ipv6 configuation dhcp+slaac
      2. Dump ipv6 routes with "ip -6 route"

      Actual results:

        Default gw has multi path pointing to each of the gateway routers ipv6 link local address

      Expected results:

        Default gw need to point to the gateway router where the VM is running, that's include the different gateway router after migration.

       

      Additional info:

       

      There are some WIP's at ovn-k fixing it while the proper OVN transit router topology lands:

       

      Proper solution is to use the future OVN topology "transit router" that's being developed here https://issues.redhat.com/browse/FDP-872.

       

       

              ellorent Felix Enrique Llorente Pastora
              ellorent Felix Enrique Llorente Pastora
              None
              None
              Anurag Saxena Anurag Saxena
              None
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

                Created:
                Updated:
                Resolved: