yahoo-eng-team team mailing list archive

[Hong Hui Xiao <xiaohhui@xxxxxxxxxx>]

Public bug reported:

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.

** Affects: neutron
     Importance: Undecided
     Assignee: Hong Hui Xiao (xiaohhui)
         Status: New


** Tags: ipv6

** Changed in: neutron
     Assignee: (unassigned) => Hong Hui Xiao (xiaohhui)

** Tags added: ipv6

-- 
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:
  New

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