Nova Docker network in container has wrong network mask

Bug #1261021 reported by Daniel Kuffner
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
OpenStack Compute (nova)
Fix Released
Medium
Daniel Kuffner

Bug Description

Network in container has wrong network mask.

In devstack you have a default network defined like following:

    nova network-list
    +--------------------------------------+---------+-------------+
    | ID | Label | Cidr |
    +--------------------------------------+---------+-------------+
    | f7c6e98d-d900-4df2-8523-0c8dd3a4ad7f | private | 10.0.0.0/24 |
    +--------------------------------------+---------+-------------+

If I start up a new container via nova and look at the created network device:

    sudo ip netns exec <container-id> ip a | grep pvnetr

    66: pvnetr70121: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP qlen 1000
        inet 10.0.0.2/8 brd 10.255.255.255 scope global pvnetr70121

Then you can see that it has a 10.0.0.2/8 network.
I would expect to find a 10.0.0.2/24

Tags: docker
affects: keystone → nova
summary: - Nova Docker network in container has wrong range
+ Nova Docker network in container has wrong networkmask
Changed in nova:
assignee: nobody → Daniel Kuffner (daniel-kuffner)
status: New → In Progress
tags: added: docker
Changed in nova:
importance: Undecided → Medium
summary: - Nova Docker network in container has wrong networkmask
+ Nova Docker network in container has wrong network mask
Revision history for this message
Daniel Kuffner (daniel-kuffner) wrote :
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to nova (master)

Reviewed: https://review.openstack.org/62220
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=709410d243a97d35c3da314b41bab039eac75736
Submitter: Jenkins
Branch: master

commit 709410d243a97d35c3da314b41bab039eac75736
Author: Daniel Kuffner <email address hidden>
Date: Sun Dec 15 09:53:17 2013 +0100

    Nova Docker: Metadata service doesn't work

    The metadata services rejects the request because the remote IP address
    belongs to the docker network. The remote IP address is correct by using
    the nova network as default route.

    Change-Id: I410a9bfea560f669515b31db7f007515b4d5c4e7
    Closes-Bug: #1259267
    Closes-Bug: #1261021

Changed in nova:
status: In Progress → Fix Committed
Changed in nova:
milestone: none → icehouse-3
Thierry Carrez (ttx)
Changed in nova:
status: Fix Committed → Fix Released
Thierry Carrez (ttx)
Changed in nova:
milestone: icehouse-3 → 2014.1
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.