Comment 79 for bug 1461054

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to neutron (stable/kilo)

Reviewed: https://review.openstack.org/194697
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=9ff6138c47c95034ba845e9448ddffd147b51f38
Submitter: Jenkins
Branch: stable/kilo

commit 9ff6138c47c95034ba845e9448ddffd147b51f38
Author: Aaron Rosen <email address hidden>
Date: Wed Jun 3 16:19:39 2015 -0700

    Provide work around for 0.0.0.0/0 ::/0 for ipset

    Previously, the ipset_manager would pass in 0.0.0.0/0 or ::/0 if
    these addresses were inputted as allowed address pairs. This causes
    ipset to raise an error as it does not work with zero prefix sizes.
    To solve this problem we use two ipset rules to represent this:

    Ipv4: 0.0.0.0/1 and 128.0.0.1/1
    IPv6: ::/1' and '8000::/1

    All of this logic is handled via _sanitize_addresses() in the ipset_manager
    which is called to convert the input.

    Conflicts:
     neutron/agent/linux/ipset_manager.py
     neutron/tests/unit/agent/linux/test_ipset_manager.py

    Change-Id: I8c6a08e0cf3b5b5386fe03af9f2174c666b8ac75
    Closes-bug: 1461054