Uploaded image for project: 'Fast Datapath Product'
  1. Fast Datapath Product
  2. FDP-697

Customer is experiencing with the integration of RedHat OpenStack Manila and NetApp storage

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Major Major
    • None
    • None
    • OVN
    • False
    • Hide

      None

      Show
      None
    • False
    • Hide

      Given a system administrator has configured OVN with the `ignore_lsp_down` setting set to false, and a logical switch port associated with the NetApp VServer is in the "DOWN" state due to its dynamic MAC address change. The logical switch port has its status reflected as "DOWN" in the OVN Port_Binding table,

      When they check the ARP reply flows for the "DOWN" port,

      Then, ARP reply flows should not be installed for the logical switch port to ensure no traffic is erroneously routed through the port when it is down.

      Show
      Given a system administrator has configured OVN with the `ignore_lsp_down` setting set to false, and a logical switch port associated with the NetApp VServer is in the "DOWN" state due to its dynamic MAC address change. The logical switch port has its status reflected as "DOWN" in the OVN Port_Binding table, When they check the ARP reply flows for the "DOWN" port, Then, ARP reply flows should not be installed for the logical switch port to ensure no traffic is erroneously routed through the port when it is down.
    • None
    • Important
    • +

      1. They created a NetApp VServer using the OpenStack Manila driver with the IP address 192.168.99.208/24. The OVN Port_Binding table shows a record with this IP and MAC binding (fa:16:3e:9e:9e:3e).
      2. On the NetApp side, the VServer during creation binds to a different MAC address (00:a0:b8:e6:b1:c8, the MAC of the physical NetApp interface). Additionally, during normal operation, the "IP-MAC" binding can change (it uses VIP, so the IP will be fixed, but the MAC will definitely change).
      3. When theyping the IP address of the OpenStack router (192.168.99.218), the responses go to the MAC address listed in the OVN Port_Binding table. These responses are visible on the NetApp physical interface.

      Could you please provide some workarounds or ideas? Perhaps we can avoid using the MAC addresses from the OVN Port_Binding table and force ARP-based resolution? Or dynamically update the MACs in the OVN Port_Binding table according to the actual VIP status on the NetApp cluster side?

      Network port details:
      openstack port list --network 5eaf3e82-8e18-41a4-a2cc-64f197f0938a -f yaml

      • Fixed IP Addresses:
      • ip_address: 192.168.99.218
        subnet_id: 4afa4295-8b40-48f2-8993-3b83bae8b51b
        ID: 1180b900-2aae-479c-9e96-6b3018a5b296
        MAC Address: fa:16:3e:65:e7:18
        Name: ''
        Status: ACTIVE
      • Fixed IP Addresses:
      • ip_address: 192.168.99.185
        subnet_id: 4afa4295-8b40-48f2-8993-3b83bae8b51b
        ID: 27929991-74df-4944-8f29-84d886c6e667
        MAC Address: fa:16:3e:d2:a6:f8
        Name: ''
        Status: N/A
      • Fixed IP Addresses:
      • ip_address: 192.168.99.171
        subnet_id: 4afa4295-8b40-48f2-8993-3b83bae8b51b
        ID: 38baf8ee-5f3a-43ff-8eb7-180de2f60b53
        MAC Address: fa:16:3e:32:65:39
        Name: ''
        Status: ACTIVE
      • Fixed IP Addresses:
      • ip_address: 192.168.99.100
        subnet_id: 4afa4295-8b40-48f2-8993-3b83bae8b51b
        ID: 46d3accf-f58d-47c5-ac42-89052f037ca2
        MAC Address: fa:16:3e:8f:67:90
        Name: ''
        Status: DOWN
      • Fixed IP Addresses:
      • ip_address: 192.168.99.208
        subnet_id: 4afa4295-8b40-48f2-8993-3b83bae8b51b
        ID: 8500fffa-1bc8-4a67-a50a-fb441f844fa3
        MAC Address: fa:16:3e:9e:9e:3e
        Name: ''
        Status: DOWN
      • Fixed IP Addresses:
      • ip_address: 192.168.99.133
        subnet_id: 4afa4295-8b40-48f2-8993-3b83bae8b51b
        ID: 979152d0-6711-47ed-97bf-36490b9fdb59
        MAC Address: 00:a0:b8:e6:b1:c8
        Name: ''
        Status: DOWN

      Define the value or impact to you or the business
      They can't use RHOSP for our production environment.

      Where are you experiencing this behavior? What environment?
      Customers can create a shared file system via Manila and attach this one to a VM.

      When does this behavior occur? Frequency? Repeatedly? At certain times?
      During the PoC configuration.

              ovnteam@redhat.com OVN Team
              rhn-support-dhill Dave Hill
              Jianlin Shi Jianlin Shi
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

                Created:
                Updated:
                Resolved: