Reviewed:  https://review.opendev.org/757107
Committed: 
https://git.openstack.org/cgit/openstack/neutron/commit/?id=0705699e6072f0862cee7749de7f7633ecc9dcfd
Submitter: Zuul
Branch:    master

commit 0705699e6072f0862cee7749de7f7633ecc9dcfd
Author: Rodolfo Alonso Hernandez <[email protected]>
Date:   Fri Oct 9 13:26:33 2020 +0000

    "scope" conversion only just before pyroute2 method call
    
    In "IpAddrCommand.list" method, the "scope" parameter is a string
    ("link", "site", "global" or "host"). This method will retrieve all
    devices with an IP address calling "ip_lib.get_devices_with_ip".
    
    Since [1], "ip_lib.get_devices_with_ip" makes the conversion of
    "scope" string parameter to pyroute2 format (see
    "pyroute2.netlink.rtnl.rtscopes"). The list command should skip then
    the previous conversion.
    
    Closes-Bug: #1899141
    
    [1]https://review.opendev.org/#/c/747406/
    
    Change-Id: I55a0f4341b328af52ea3bd758a72f633fbe3abcb


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

Title:
  Linuxbridge agent NetlinkError: (13, 'Permission denied') after Stein
  upgrade

Status in neutron:
  Fix Released

Bug description:
  OpenStack-Ansible deployment, just upgraded to Stein, using Ubuntu
  18.04.

  Neutron Linuxbridge agent logs keep complaining about NetlinkError: (13, 
'Permission denied').
  After enabling debug, we actually see two stack traces, one happening in 
privsep, see log attached.

  We found out disabling IPv6 on the host workarounds the problem, but
  that's not a proper fix of course.

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

-- 
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to     : [email protected]
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help   : https://help.launchpad.net/ListHelp

Reply via email to