← Back to team overview

yahoo-eng-team team mailing list archive

[Bug 2125569] Re: [OVN] The method to sync the HA_Chassis_Group should always update the "ignore_chassis" variable

 

Reviewed:  https://review.opendev.org/c/openstack/neutron/+/962191
Committed: https://opendev.org/openstack/neutron/commit/4238ccb45069eb75c1af960d367080e731414a8d
Submitter: "Zuul (22348)"
Branch:    master

commit 4238ccb45069eb75c1af960d367080e731414a8d
Author: Rodolfo Alonso Hernandez <ralonsoh@xxxxxxxxxx>
Date:   Wed Sep 24 11:49:21 2025 +0000

    [OVN] Always exclude the local chassis creating ``HA_Chassis_Group``
    
    When a ``HA_Chassis_Group`` for an external port is created, the method
    always discards the chassis bound to the port. A logical port can have
    several chassis stored in the ``Port_Binding`` register, in the ``name``
    field (the main one) and in the ``additional_chassis`` list (see method
    ``get_chassis_host_for_port``).
    
    Closes-Bug: #2125569
    Signed-off-by: Rodolfo Alonso Hernandez <ralonsoh@xxxxxxxxxx>
    Change-Id: I3346c2a16f69c3b16d1693db42335b133a721bf9


** Changed in: neutron
       Status: In Progress => Fix Released

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/2125569

Title:
  [OVN] The method to sync the HA_Chassis_Group should always update the
  "ignore_chassis" variable

Status in neutron:
  Fix Released

Bug description:
  The method ``sync_ha_chassis_group_network`` [1] is used to create a
  "HA_Chassis_Group" for an external port. If the OVN cluster has
  chassis with the "other_config:ovn-cms-options:enable-chassis-as-
  extport-host" flag, these chassis are used first to bind the external
  port. In this case, the method excludes the local chassis where the VM
  with the external port (SR-IOV) is located.

  However, if the cluster doesn't have these chassis and only has
  "regular" external chassis (those with "other_config:ovn-cms-
  options:enable-chassis-as-gw" flag), the method does not exclude the
  chassis where the VM is located.

  This assumption works almost always because the "regular" external
  chassis are networker or controller nodes, not compute nodes. However,
  in some scenarios (mostly testing), the same node that hosts the VM
  with the external port can also be an external gateway chassis.

  This bug proposed to always exclude the local chassis regardless of
  the GW chassis list built.

  [1]https://github.com/openstack/neutron/blob/e0ca9a0d68fbbcb98820f488accf2f84fb8c9639/neutron/common/ovn/utils.py#L1203-L1233

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/2125569/+subscriptions



References