openstack team mailing list archive
-
openstack team
-
Mailing list archive
-
Message #23259
Re: OpenStack Folsom Install - VM failed to configure network
I have looked through all the log files (/var/log/*) and the 1 error that
I do see is on the compute node from the file libvirtd.log:
2013-05-03 14:30:27.706+0000: 2474: error : virNWFilterDHCPSnoopEnd:2113 :
internal error ifname "vnet1" not in key map
2013-05-03 14:30:27.709+0000: 2474: error : virNetDevGetIndex:657 : Unable
to get index for interface vnet1: No such device
Can anyone point me in the right direction (or suggest some way of
debugging this)
Many Thanks,
-Farhan.
On 5/2/13 4:01 PM, "Farhan Patwa" <Farhan.Patwa@xxxxxxxx> wrote:
>Hi all,
>I followed the instructions for OpenStack Folsom install at
>http://docs.openstack.org/folsom/basic-install/content/basic-install_intro
>.
>html
>I am at the point where I am able to boot up a VM and I can see the IP
>assigned to it in the GUI and when I do nova list.
>Also I have assigned a floating IP to it using the quantum commands
>specified in the guide above.
>But when I boot the VM I get the logs below.
>The tap device is UP and I am able to ping the 3 servers on the management
>LAN and the 2 servers (network and compute) on their data network.
>I would really appreciate any help/pointers that anyone can provide.
>
>#################################################################
>cloud-init start-local running: Thu, 02 May 2013 20:10:55 +0000. up 3.74
>seconds
>
>no instance data found in start-local
>
>cloud-init-nonet waiting 120 seconds for a network device.
>
>cloud-init-nonet gave up waiting for a network device.
>
>ci-info: lo : 1 127.0.0.1 255.0.0.0 .
>
>ci-info: eth0 : 1 . . fa:16:3e:9e:88:7d
>
>route_info failed
>
> * Stopping Handle applying cloud-config[74G[ OK ]
>
>Waiting for network configuration...
>
>Waiting up to 60 more seconds for network configuration...
>
>Booting system without full network configuration...
>
> * Stopping Failsafe Boot Delay[74G[ OK ]
>
> * Starting System V initialisation compatibility[74G[ OK ]
>
>Skipping profile in /etc/apparmor.d/disable: usr.sbin.rsyslogd
>
> * Starting AppArmor profiles [80G
>[74G[ OK ]
>
>#################################################################
>
>Thanks,
>
>
>-Farhan Patwa.
>
>
>
>_______________________________________________
>Mailing list: https://launchpad.net/~openstack
>Post to : openstack@xxxxxxxxxxxxxxxxxxx
>Unsubscribe : https://launchpad.net/~openstack
>More help : https://help.launchpad.net/ListHelp
>
Follow ups
References