yahoo-eng-team team mailing list archive

[OpenStack Infra <1983530@xxxxxxxxxxxxxxxxxx>]

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

commit e0039371f876fe7ca52d4c49c997be0c73b80adf
Author: zhouhenglc <zhouhenglc@xxxxxxxxxx>
Date:   Thu Aug 4 08:47:10 2022 +0800

    [ovn]Change LogicalSwitchPortUpdateUpEvent old conditions
    
    Sometimes when creating ports, the status of logical_switch_port
    changes from [] to [true]. we should be able to deal with this
    situation and ensure that the port is in the active state in neutron.
    
    Closes-bug: #1983530
    
    Change-Id: I99d2a8078dd7acde72b232a5b1de826d7e1d60f3


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

Title:
  [ovn]router_interface port probability cannot be up

Status in neutron:
  Fix Released

Bug description:
  I have en environment, with 5 neutron-server(W version), 5
  ovn(21.03.1)

  When adding an interface to the router, the state of the interface is sometimes down,
  and it will not become up after a long time. Restarting the neutron server can become up.

  I check logical_switch_port by "ovn-nbctl list logical_switch_port <port-id>",  the status
  of lsp is up, and the traffic can be forwarded normally.

  This should only be a neutron save state problem.

  In the past, when creating vm, the ports have been unable to be up, and the reason has not
  been found. The phenomenon is the same as that of the router interface.

  In the process of adding a routing interface, I wrote a script to listen to logical_switch_port
  change, I found: before lsp becomes up=true, lsp's up=[], which is not up=[false], not 
  matchd LogicalSwitchPortUpdateUpEvent. I don't know why ovn's notification events are 
  sometimes different, but I think it should be repaired here in neutron

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