yahoo-eng-team team mailing list archive

[Daniel Kuffner <daniel.kuffner@xxxxxxxxx>]

Public bug reported:


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

** Affects: keystone
     Importance: Undecided
         Status: New

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to Keystone.
https://bugs.launchpad.net/bugs/1261021

Title:
  Nova Docker network in container has wrong range

Status in OpenStack Identity (Keystone):
  New

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

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