← Back to team overview

yahoo-eng-team team mailing list archive

[Bug 1787919] Re: Upgrade router to L3 HA broke IPv6

 

Reviewed:  https://review.openstack.org/613396
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=b847cd02c56dc8fe654f4731306dc2b5493a62eb
Submitter: Zuul
Branch:    master

commit b847cd02c56dc8fe654f4731306dc2b5493a62eb
Author: Brian Haley <bhaley@xxxxxxxxxx>
Date:   Thu Oct 25 14:41:19 2018 -0400

    Enable 'all' IPv6 forwarding knob correctly
    
    When the external gateway is plugged and we enable IPv6
    forwarding on it, make sure the 'all' sysctl knob is also
    enabled, else IPv6 packets will not be forwarded.  This
    seems to only affect HA routers that default to disabling
    this 'all' knob on creation.
    
    Also, when we are removing all the IPv6 addresses from a
    HA router internal interface, set 'accept_ra' to zero so
    it doesn't accidentally auto-configure an address.  Set
    it back to one when adding them back.
    
    Re-homed newly added _wait_until_ipv6_forwarding_has_state()
    accordingly.
    
    Closes-bug: #1787919
    
    Change-Id: Ia1f311ee31d1479089685367a97bf13cf170b342


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

Title:
  Upgrade router to L3 HA broke IPv6

Status in neutron:
  Fix Released

Bug description:
  When I disabled a router, changed it to L3 HA and enabled it again all
  the logic that was implemented in [1] did not seem to work.

  Please see the thread on ML [2] for details.
  The backup router had the net.ipv6.conf.qr-<interface>.accept_ra values for the qr interfaces (one for ipv4 and one for ipv6) set to 1.

  On the active router the net.ipv6.conf.all.forwarding option was set
  to 0.

  After removing SLAAC addresses on the backup router, setting accept_ra
  to 0 and enabling ipv6 forwarding on the active router it started
  working again.

  Please let me know if you need anything to troubleshoot this here or
  on IRC (tobias-urdin).

  Best regards
  Tobias

  [1] https://review.openstack.org/#/q/topic:bug/1667756+(status:open+OR+status:merged
  [2] http://lists.openstack.org/pipermail/openstack-dev/2018-August/133499.html

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


References