RDO tickets are now tracked in Jira https://issues.redhat.com/projects/RDO/issues/
Bug 1377622 - Neutron: IPv6 Prefix delegation - failure to start dibbler due to missing rootwrap filter
Summary: Neutron: IPv6 Prefix delegation - failure to start dibbler due to missing roo...
Keywords:
Status: CLOSED NEXTRELEASE
Alias: None
Product: RDO
Classification: Community
Component: openstack-neutron
Version: Mitaka
Hardware: Unspecified
OS: Linux
medium
high
Target Milestone: ---
: trunk
Assignee: Bernard Cafarelli
QA Contact: Ofer Blaut
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-09-20 08:45 UTC by Thomas Ries
Modified: 2016-09-23 15:12 UTC (History)
3 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2016-09-23 15:12:11 UTC
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Launchpad 1626132 0 None None None 2016-09-21 14:52:00 UTC
RDO 2641 0 None None None 2016-09-22 10:51:13 UTC

Description Thomas Ries 2016-09-20 08:45:31 UTC
Description of problem:
When enabling IPv6 Prefix delegation, Neutron L3 agent is unable to start dibbler-client to fetch an IPv6 prefix from an upstream router.
There seems to be a rootwrap filter file missing (dibbler.filters), a failure when l3-agents want to launch a dibbler instance.


Version-Release number of selected component (if applicable):
openstack-neutron-common-8.1.2-1.el7.noarch
openstack-neutron-8.1.2-1.el7.noarch


How reproducible:
Always.


Steps to Reproduce:
1. /etc/neutron/neutron.conf: ipv6_pd_enabled = true
2. create a default IPv6 pool
   $ neutron subnetpool-create --shared --pool-prefix 2a01:xxxx:yyyy::/48 \
           --default-prefixlen 64 --is-default true prefix_delegation
3. create a tenant IPv6 network
   $ neutron net-create ipv6-pd
4. create a tenant IPv6 subnet using the above default pool
   $ neutron subnet-create ipv6-pd --name ipv6-pd-1 --ip_version 6 --ipv6_ra_mode slaac --ipv6_address_mode slaac --use_default_subnetpool
5. create a tenant router
6. attach tenant router to tenant network


Actual results:
No dibbler client instance is launched on network node.


Expected results:
A dibbler client instance is launched within the correct netns namespace.


Additional info:
Manually fetching the missing dibbler.filter file from openstack-neutron GIT repo <https://github.com/openstack/neutron/blob/master/etc/neutron/rootwrap.d/dibbler.filters> and placing it into /etc/neutron/rootwrap.d/ does solve the issue.

Comment 1 Assaf Muller 2016-09-20 10:45:12 UTC
@Bernard it looks like it may be a packaging issue, the dibbler.filters file is not being placed in the correct place.

Comment 2 Bernard Cafarelli 2016-09-21 13:00:34 UTC
Indeed, and it is the only rootwrap filter currently missing in packaging.

The spec file does not use a wildcard for these files, as some belong to specific packages (openvswitch and linuxbridge) while the others come with the common neutron package. I will add the dibbler.filters one to this list

Comment 3 Bernard Cafarelli 2016-09-23 15:12:11 UTC
As detailed in the linked bugs, it turned out the file was not installed upstream, so did not end up in the RPM.

This is now fixed upstream in master and stable branches from Liberty to Newton, and in RDO in rpm-master, rpm-mitaka, rpm-liberty


Note You need to log in before you can comment on or make changes to this bug.