yahoo-eng-team team mailing list archive

[OpenStack Infra <1974183@xxxxxxxxxxxxxxxxxx>]

Reviewed:  https://review.opendev.org/c/openstack/neutron/+/843247
Committed: https://opendev.org/openstack/neutron/commit/68bbd3586bdc313a6b67f2983ba2331a7956856c
Submitter: "Zuul (22348)"
Branch:    master

commit 68bbd3586bdc313a6b67f2983ba2331a7956856c
Author: Rodolfo Alonso Hernandez <ralonsoh@xxxxxxxxxx>
Date:   Sat May 14 09:41:25 2022 +0000

    [Trunk] Check if parent port belongs to OVN to activate
    
    In Trunk service, the OVN was setting always the trunk to "ACTIVE"
    anytime the trunk was created or updated. This patch changes this
    behaviour: only when the trunk parent port belongs to OVN (that
    means, there is a related logical switch port to this Neutron port),
    the methods will set the trunk to "ACTIVE".
    
    Closes-Bug: #1974183
    Change-Id: Ied5ef53882d4249e0ceaa731239befdc3ba67d03


** 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/1974183

Title:
  Neutron allows creation of trunks for VIF_TYPE_HW_VEB ports

Status in neutron:
  Fix Released

Bug description:
  There's no trunk driver supporting VIF_TYPE_HW_VEB ports [1,2,3], yet
  Neutron allows trunks to be created for them. I think it should
  rejected on validation.

  [1] https://github.com/openstack/neutron/blob/b1f48d8da3a6017a49f2a9ece89b9dc01ba8a810/neutron/services/trunk/drivers/openvswitch/driver.py#L31-L34
  [2] https://github.com/openstack/neutron/blob/b1f48d8da3a6017a49f2a9ece89b9dc01ba8a810/neutron/services/trunk/drivers/ovn/trunk_driver.py#L29-L32
  [3] https://github.com/openstack/neutron/blob/b1f48d8da3a6017a49f2a9ece89b9dc01ba8a810/neutron/services/trunk/drivers/linuxbridge/driver.py#L25-L27

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