openstack team mailing list archive

[Arindam Choudhury <arindam@xxxxxxxx>]

I am getting these errors in compute node:

  
2013-07-11T23:22:12Z|00301|bridge|INFO|bridge br-int: added interface qvo891434de-33 on port 5
2013-07-11T23:22:12Z|00302|netdev_linux|ERR|ioctl(SIOCSIFHWADDR) on br-ex device failed: Device or resource busy
2013-07-11T23:22:12Z|00303|bridge|ERR|Dropped 8 log messages in last 261 seconds (most recently, 241 seconds ago) due to excessive rate
2013-07-11T23:22:12Z|00304|bridge|ERR|bridge br-ex: failed to set bridge Ethernet address: Device or resource busy
2013-07-11T23:22:12Z|00305|netdev_linux|ERR|ioctl(SIOCSIFHWADDR) on br-eth1 device failed: Device or resource busy
2013-07-11T23:22:12Z|00306|bridge|ERR|bridge br-eth1: failed to set bridge Ethernet address: Device or resource busy
2013-07-11T23:22:12Z|00307|netdev_linux|ERR|ioctl(SIOCSIFHWADDR) on br-int device failed: Device or resource busy
2013-07-11T23:22:12Z|00308|bridge|ERR|bridge br-int: failed to set bridge Ethernet address: Device or resource busy
2013-07-11T23:22:18Z|00309|netdev_linux|ERR|ioctl(SIOCSIFHWADDR) on br-ex device failed: Device or resource busy
2013-07-11T23:22:18Z|00310|bridge|ERR|bridge br-ex: failed to set bridge Ethernet address: Device or resource busy
2013-07-11T23:22:18Z|00311|netdev_linux|ERR|ioctl(SIOCSIFHWADDR) on br-eth1 device failed: Device or resource busy
2013-07-11T23:22:18Z|00312|netdev_linux|ERR|ioctl(SIOCSIFHWADDR) on br-int device failed: Device or resource busy
2013-07-11T23:22:28Z|00313|ofproto|INFO|br-eth1: 1 flow_mods 10 s ago (1 adds)
2013-07-11T23:22:28Z|00314|ofproto|INFO|br-int: 2 flow_mods in the 1 s starting 10 s ago (1 adds, 1 deletes)
^C
[root@sl-2 ~]# ovs-vsctl show
5548cd68-c4a4-4edd-945f-13983da20067
    Bridge br-ex
        Port br-ex
            Interface br-ex
                type: internal
    Bridge "br-eth1"
        Port "br-eth1"
            Interface "br-eth1"
                type: internal
    Bridge br-int
        Port "qvo891434de-33"
            tag: 4
            Interface "qvo891434de-33"
        Port br-int
            Interface br-int
                type: internal
    ovs_version: "1.10.0"
  

		

From: arindam@xxxxxxxx
To: openstack@xxxxxxxxxxxxxxxxxxx
Date: Thu, 11 Jul 2013 23:09:11 +0200
Subject: [Openstack] faile scheduling network in quantum vlan





			hi,


I used packstack to make a two node openstack deployment with quantum(vlan) on Scientific linux 6.


  
I configured EPEL using: rpm -Uvh http://mirror.uv.es/mirror/fedora-epel/6/x86_64/epel-release-6-8.noarch.rpm
I upgraded the dnsmasq using:  yum install http://ftp.is.co.za/mirror/ftp.rpmforge.net/redhat/el6/en/x86_64/extras/RPMS/dnsmasq-2.65-1.el6.rfx.x86_64.rpm



Then I changed the following in the generated answer file to enable quantum vlan:


  
CONFIG_QUANTUM_OVS_TENANT_NETWORK_TYPE=vlan
CONFIG_QUANTUM_OVS_VLAN_RANGES=default:100:110
CONFIG_QUANTUM_OVS_BRIDGE_MAPPINGS=default:br-ex



Then I created a non-admin user and followed this http://docs.openstack.org/grizzly/openstack-network/admin/content/demo_logical_network_config.html  tutorial to create the networks.


  
[arindam@sl-1 ~(keystone_user)]$ quantum net-list
+--------------------------------------+---------+--------------------------------------------------+
| id                                   | name    | subnets                                          |
+--------------------------------------+---------+--------------------------------------------------+
| 06614a9a-0ccd-47a8-996d-c7a6b2a6a605 | ext_net | 2c864957-09c9-4067-82de-64ad0da3ed41             |
| 66e0a1bc-0852-4cd4-9f11-aac57ed74d53 | net1    | 761103ea-1b0d-41f1-9a40-39bd14aaf99d 10.5.5.0/24 |
+--------------------------------------+---------+--------------------------------------------------+
[arindam@sl-1 ~(keystone_user)]$ quantum router-list
+--------------------------------------+---------+--------------------------------------------------------+
| id                                   | name    | external_gateway_info                                  |
+--------------------------------------+---------+--------------------------------------------------------+
| 2cb10a37-48bf-48f1-bf22-b5e255deba44 | router1 | {"network_id": "06614a9a-0ccd-47a8-996d-c7a6b2a6a605"} |
+--------------------------------------+---------+--------------------------------------------------------+
[arindam@sl-1 ~(keystone_user)]$ quantum router-port-list 2cb10a37-48bf-48f1-bf22-b5e255deba44
+--------------------------------------+------+-------------------+---------------------------------------------------------------------------------+
| id                                   | name | mac_address       | fixed_ips                                                                       |
+--------------------------------------+------+-------------------+---------------------------------------------------------------------------------+
| 2e77fa36-3127-414b-bfcf-d8dd6cd568be |      | fa:16:3e:fd:3e:16 | {"subnet_id": "761103ea-1b0d-41f1-9a40-39bd14aaf99d", "ip_address": "10.5.5.1"} |
+--------------------------------------+------+-------------------+---------------------------------------------------------------------------------+



but when I instantiate a virtual machine, it does not get ip address.



2013-07-11 22:45:49  WARNING [quantum.db.agentschedulers_db] Fail 
scheduling network {'status': u'ACTIVE', 'subnets': 
[u'761103ea-1b0d-41f1-9a40-39bd14aaf99d'], 'name': u'net1', 
'provider:physical_network': u'default', 'admin_state_up': True, 
'tenant_id': u'335c80bb3f304bdcb987c27eaf8eb364', 
'provider:network_type': u'vlan', 'router:external': False, 'shared': 
False, 'id': u'66e0a1bc-0852-4cd4-9f11-aac57ed74d53', 
'provider:segmentation_id': 101L}
  

		 		 	   		  

_______________________________________________
Mailing list: https://launchpad.net/~openstack
Post to     : openstack@xxxxxxxxxxxxxxxxxxx
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp