yahoo-eng-team team mailing list archive

[OpenStack Infra <2078789@xxxxxxxxxxxxxxxxxx>]

Reviewed:  https://review.opendev.org/c/openstack/neutron/+/927795
Committed: https://opendev.org/openstack/neutron/commit/8211c29158d6fc8a1af938c326dfbaa685428a4a
Submitter: "Zuul (22348)"
Branch:    master

commit 8211c29158d6fc8a1af938c326dfbaa685428a4a
Author: Rodolfo Alonso Hernandez <ralonsoh@xxxxxxxxxx>
Date:   Tue Sep 3 09:30:54 2024 +0000

    [SR-IOV] The port status=DOWN has precedence in the VF link status
    
    If a ML2/SR-IOV port is disabled (status=DOWN), it will have precedence
    on the VF link state value over the "auto" value. That will stop any
    transmission from the VF.
    
    Closes-Bug: #2078789
    Change-Id: I11d973d245dd391623e501aa14b470daa780b4db


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

Title:
  [SR-IOV] The "auto" VF status has precedence over the
  "enable"/"disable" status

Status in neutron:
  Fix Released

Bug description:
  This bug only applies to ML2/SR-IOV.

  The port field "propagate_uplink_status" defines if the port (VF) will
  follow the parent port (PF) status (enabled/disabled). The "auto"
  status has precedence over the "enable"/"disable" status. However,
  this could be a security issue: if the port owner wants to stop the VF
  (VM port) from transmitting any traffic, it is needed first to unset
  the "propagate_uplink_status" field [1] and the set the port status to
  "disabled".

  Scope of this bug: The "disabled" status must have precedence over the
  "auto" or "enabled" statuses, for security reasons.

  
  [1]https://bugs.launchpad.net/neutron/+bug/2078661

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