Uploaded image for project: 'netvirt'
  1. netvirt
  2. NETVIRT-268

Floating IP rules installed with wrong actions

    XMLWordPrintable

Details

    • Bug
    • Status: Resolved
    • Resolution: Done
    • Boron
    • None
    • General
    • None
    • Operating System: Linux
      Platform: All

    • 7165

    Description

      I have a setup with 3 OpenStack controllers, 1 Karaf and 2 compute nodes.
      I have constructed the following topology:
      two private networks(each configured with vxlan) and one external network connected to one router.
      each private network has one VM.

      Ping between vms work fine.
      Ping to floating IP (of either vms) doesn't work.

      I have investigated the first floating ip, 10.83.5.112, which is used by a vm on compute 1. In the ovs dump flows of compute 1, I see the following flow:

      cookie=0x8000003, duration=6378.900s, table=21, n_packets=66, n_bytes=5868, priority=42,ip,metadata=0x222e0/0xfffffffe,nw_dst=10.83.5.112 actions=write_actions(set_field:0x11245->tun_id,output:5)

      port number 5 is a tunnel port and not a "vm" port.

      Dump model of config/odl-fib:fibEntries/ shows:
      {
      "destPrefix": "10.83.5.112/32",
      "label": 70213,
      "nextHopAddressList": [
      "10.83.6.5",
      "10.83.6.6"
      ],
      "origin": "s"
      },

      10.83.6.5 is compute1 IP, 10.83.6.6 is compute2 IP.

      Attachments

        No reviews matched the request. Check your Options in the drop-down menu of this sections header.

        Activity

          People

            Unassigned Unassigned
            ofer.barber@hpe.com ofer barber
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: