Uploaded image for project: 'Red Hat OpenStack Services on OpenShift'
  1. Red Hat OpenStack Services on OpenShift
  2. OSPRH-12911

BZ#2282209 FIP bound with VIP is not working on [RHOSP16.2.6

XMLWordPrintable

    • False
    • False
    • No Docs Impact
    • python-networking-ovn-7.4.2-2.20220409154886.el8ost
    • None
    • Hide
      Cause: Virtual ports created with a custom device_owner was loosing the type.virtual on OVN NB DB as soon traffic was sent/received over it.

      Consequence: The Port Binding associated to the VIP port is recreated as soon Virtual Port change the type. Loosing the Chassis and virtual-parents info. In DVR envs, with distributed Floating IP, traffic over the FIP attached to the VIP is not replied.

      Fix: Virtual ports that would be use to redirect traffic over VM ports needs to be created using device_owner value of 'virtual_port'. Special case for Octavia, that is creating VIP LB ports using device_owner 'Octavia' is also covered.
      Show
      Cause: Virtual ports created with a custom device_owner was loosing the type.virtual on OVN NB DB as soon traffic was sent/received over it. Consequence: The Port Binding associated to the VIP port is recreated as soon Virtual Port change the type. Loosing the Chassis and virtual-parents info. In DVR envs, with distributed Floating IP, traffic over the FIP attached to the VIP is not replied. Fix: Virtual ports that would be use to redirect traffic over VM ports needs to be created using device_owner value of 'virtual_port'. Special case for Octavia, that is creating VIP LB ports using device_owner 'Octavia' is also covered.
    • Bug Fix
    • Proposed
    • Moderate

      Description of problem:
      After the update from 16.2.2 to 16.2.6 the FIP attached to a VIP seems not working anymore.

      Version-Release number of selected component (if applicable):
      Red Hat Openstack 16.2.6

      Steps to Reproduce:
      1. create a VIP port with owner neutron:LOADBALANCER
      2. associate a FIP to that VIP
      3. Add allowed-address pair for the VIP associated with instance port
      4. add the ip to the os
      5. ping or anything else with the FIP
      6. from VIP side it's working
      7. disable port security on VIP and the FIP is working working

      Note from last test we notice that after the association was working and after a while stop working. ~14:48 CET time 21 of May

      Actual results:
      FIP attached to a VIP is not reachable

      Expected results:
      FIP attached to a VIP is reachable

      Additional info:

          There are no Sub-Tasks for this issue.

              froyo@redhat.com Fernando Royo
              jira-bugzilla-migration RH Bugzilla Integration
              rhos-dfg-networking-squad-neutron
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

                Created:
                Updated:
                Resolved: