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

Failed to reach pod over IPv6 address on SR-IOV interface

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Obsolete
    • Icon: Undefined Undefined
    • None
    • 4.16
    • Networking / SR-IOV
    • None
    • Moderate
    • None
    • CNF Network Sprint 255
    • 1
    • False
    • Hide

      None

      Show
      None

      Description of problem:

      Failed to reach workload over IPv6 address on SR-IOV network:

       

      oc logs -n rds-sriov-wlkd rdscore-sriov-one-5f49556746-jhx82
      lo               UNKNOWN        127.0.0.1/8 ::1/128
      gre0@NONE        DOWN
      gretap0@NONE     DOWN
      erspan0@NONE     DOWN
      eth0@if70        UP             10.131.0.15/23 fd01:0:0:4::f/64 fe80::858:aff:fe83:f/64
      net1.497@net1    UP             10.46.126.75/26 2620:52:0:2e7e::41/122 fe80::4427:66ff:fecd:fca/64
      net1             UP             fe80::4427:66ff:fecd:fca/64
      + sleep 1
      + nc -k -l 1111
      oc logs -n rds-sriov-wlkd rdscore-sriov-two-7bd457d75f-tfb54
      lo               UNKNOWN        127.0.0.1/8 ::1/128
      gre0@NONE        DOWN
      gretap0@NONE     DOWN
      erspan0@NONE     DOWN
      eth0@if71        UP             10.131.0.16/23 fd01:0:0:4::10/64 fe80::858:aff:fe83:10/64
      net1.497@net1    UP             10.46.126.77/26 2620:52:0:2e7e::42/122 fe80::fc25:41ff:fe47:b33c/64
      net1             UP             fe80::fc25:41ff:fe47:b33c/64
      + sleep 1
      + nc -k -l 1111 
      oc rsh -n rds-sriov-wlkd rdscore-sriov-one-5f49556746-jhx82
      
      sh-5.2# echo "IPv4 from ${HOSTNAME}" | nc 10.46.126.77 1111
      sh-5.2# echo "IPv6 from ${HOSTNAME}" | nc 2620:52:0:2e7e::42 1111
      Ncat: No route to host.
      
      sh-5.2# ip r
      default via 10.131.0.1 dev eth0
      10.46.126.64/26 dev net1.497 proto kernel scope link src 10.46.126.75
      10.128.0.0/14 via 10.131.0.1 dev eth0
      10.131.0.0/23 dev eth0 proto kernel scope link src 10.131.0.15
      100.64.0.0/16 via 10.131.0.1 dev eth0
      172.30.0.0/16 via 10.131.0.1 dev eth0
      
      sh-5.2# ip -6 r
      2620:52:0:2e7e::40/122 dev net1.497 proto kernel metric 256 pref medium
      fd01:0:0:4::/64 dev eth0 proto kernel metric 256 pref medium
      fd01::/48 via fd01:0:0:4::1 dev eth0 metric 1024 pref medium
      fd02::/112 via fd01:0:0:4::1 dev eth0 metric 1024 pref medium
      fd98::/64 via fd01:0:0:4::1 dev eth0 metric 1024 pref medium
      fe80::/64 dev eth0 proto kernel metric 256 pref medium
      fe80::/64 dev net1 proto kernel metric 256 pref medium
      fe80::/64 dev net1.497 proto kernel metric 256 pref medium
      default via fd01:0:0:4::1 dev eth0 metric 1024 pref medium
      sh-5.2# 

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

      sriov-network-operator.v4.16.0-202405212036

      How reproducible:

      not always

      Steps to Reproduce:

      1. Deploy baremetal dualstack cluster
      2. Install and configure SR-IOV operator
      3. Create SR-IOV network and SR-IOV network node policy
      4. Create workload that uses SR-IOV and configure both IPv4 and IPv6 addresses on the interface
      5. Try to reach interface via IPv4 and IPv6 addresses configured on it

      Actual results:

      Workload reachable via IPv4 address but not over IPv6

      Expected results:

      Workload reachable via both IPv4 and IPv6 addresses

      Additional info:

       

            apanatto@redhat.com Andrea Panattoni
            yprokule@redhat.com Yurii Prokulevych
            Zhanqi Zhao Zhanqi Zhao
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: