yahoo-eng-team team mailing list archive

[OpenStack Infra <1555027@xxxxxxxxxxxxxxxxxx>]

Reviewed:  https://review.openstack.org/312890
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=42b209a6f9918c9fe8a96462b85278569a1cc85d
Submitter: Jenkins
Branch:    master

commit 42b209a6f9918c9fe8a96462b85278569a1cc85d
Author: Hong Hui Xiao <honghui_xiao@xxxxxxxx>
Date:   Sat Aug 20 08:09:54 2016 -0400

    Fix security_groups_provider_updated for linuxbridge
    
    According to [1], security_groups_provider_updated will get port ids
    to update the related security groups.
    
    However, in the firewall of l2 agent, ports are identified by 'device'
    attribute. This is fine for ovs agent, because, for ovs agent, port id
    is the same as 'device' attribute.
    
    But for other agent, like linuxbridge agent, the 'device' attribute of
    port will be the device name. This will make l2 agent can't find port
    and fail to update the security group of port. The info message at [2]
    can be observed.
    
    The fix is to convert port id list to 'device' list.
    
    [1] http://git.openstack.org/cgit/openstack/neutron/tree/neutron/db/securitygroups_rpc_base.py#n157
    [2] http://git.openstack.org/cgit/openstack/neutron/tree/neutron/agent/linux/iptables_firewall.py#n177
    
    Change-Id: Idf9bd7942ef2063cfbc5e9eeead8d49d09883ea8
    Closes-Bug: #1555027


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

Title:
  Can't get IPV6 address from radvd when router interface is added after
  vm creation

Status in neutron:
  Fix Released

Bug description:
  Env: upstream code with linux bridge agent

  Steps to reproduce:
  1) Create network
  2) create ipv4 and ipv6 subnet(ipv6_address_mode:slaac,  ipv6_ra_mode:slaac )
  3) boot vm in the network
  4) Add subnet(both ipv4 and ipv6) as router interfaces
  5) Check the vm's IPV6 address

  Expected: the vm has ipv6 address config and usable
  Actual: the ipv6 prefix which should come from radvd is not configed to vm

  Reboot vm will not help. Boot another vm in the subnet can get ipv6
  address for both of them

  radvdump in router namespace can get the RA information of subnets.

  Compared the ip6tables, there is one rule missed:
   
  Chain neutron-linuxbri-id7a6cff0-e (1 references)
      1   104 RETURN     icmpv6    *      *       fe80::f816:3eff:fe4e:eb56  ::/0                 ipv6-icmptype 134

  Boot another vm will make this rule added, add it manually will also
  make things right.

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