← Back to team overview

yahoo-eng-team team mailing list archive

[Bug 1062442] Re: Log a warning when filtering out vlan networks in FlatDHCPManager

 

** Changed in: nova
       Status: Confirmed => Opinion

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
https://bugs.launchpad.net/bugs/1062442

Title:
  Log a warning when filtering out vlan networks in FlatDHCPManager

Status in OpenStack Compute (Nova):
  Opinion

Bug description:
  My compute node machine is RHEL6.3 and openstack is Essex release and
  I am using nova-network, I create a network like this on my controller
  node:

  mysql> select * from networks\G
  *************************** 1. row ***************************
           created_at: 2012-10-04 14:41:46
           updated_at: NULL
           deleted_at: NULL
              deleted: 0
                   id: 1
             injected: 0
                 cidr: 172.17.33.0/24
              netmask: 255.255.255.0
               bridge: br100
              gateway: 172.17.33.1
            broadcast: 172.17.33.255
                 dns1: NULL
                 vlan: 100
   vpn_public_address: NULL
      vpn_public_port: 1000
  vpn_private_address: 172.17.33.2
           dhcp_start: 172.17.33.3
           project_id: d46b73631d044e009cc84702b21512e0
                 host: NULL
              cidr_v6: NULL
           gateway_v6: NULL
                label: public
           netmask_v6: NULL
     bridge_interface: eth0
           multi_host: 1
                 dns2: NULL
                 uuid: ce576fdf-c41a-40ae-a4a9-8aa14201b4cc
             priority: NULL
            rxtx_base: NULL
  1 row in set (0.00 sec)

  
  In the network.log file, I got following messages:

  2012-10-04 10:55:47 DEBUG nova.network.manager [req-500879b3-ec73-4a0b-9fd0-502e97e4efe6 a0227cff64ca4b35a4e0f5109b9f8567 d46b73631d044e009cc84702b21512e0] network allocations for instance |1| from (pid=4303) allocate_for_instance /usr/lib/python2.6/site-packages/nova/network/manager.py:896
  2012-10-04 10:55:47 DEBUG nova.network.manager [req-500879b3-ec73-4a0b-9fd0-502e97e4efe6 a0227cff64ca4b35a4e0f5109b9f8567 d46b73631d044e009cc84702b21512e0] networks retrieved for instance |1|: |[]| from (pid=4303) allocate_for_instance /usr/lib/python2.6/site-packages/nova/network/manager.py:902
  2012-10-04 10:55:47 DEBUG nova.rpc.amqp [req-500879b3-ec73-4a0b-9fd0-502e97e4efe6 a0227cff64ca4b35a4e0f5109b9f8567 d46b73631d044e009cc84702b21512e0] Pool creating new connection from (pid=4303) create /usr/lib/python2.6/site-packages/nova/rpc/amqp.py:60

  The network info is empty, and on this compute node, the br100 and
  dnsmasq process can not be started automatically.

  Have any idea about this? need I create the bridge manually?


  I find the root cause is:
  When I try to create network the vlan is set by default and it will be filtered out under FloatDHCP mode. 

  And there are no any friendly messages or document to show me what
  happened when I create network or launch instance.

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