route_info failed

Bug #1089791 reported by wangyan
10
This bug affects 2 people
Affects Status Importance Assigned to Milestone
nova (Ubuntu)
Expired
Undecided
Unassigned

Bug Description

We has instances in our dashboard,But we the instances haven't get Ip address when we use fixed ip
The issue has been properly described in the following :
[ 0.944475] FDC 0 is a S82078B
Begin: Running /scripts/local-premount ... done.
[ 1.138715] EXT4-fs (vda1): mounted filesystem with ordered data mode. Opts: (null)
Begin: Running /scripts/local-bottom ... done.
done.
Begin: Running /scripts/init-bottom ... done.
[ 1.220257] Refined TSC clocksource calibration: 2000.070 MHz.
[ 2.022836] EXT4-fs (vda1): re-mounted. Opts: (null)
cloud-init start-local running: Thu, 13 Dec 2012 06:26:35 +0000. up 3.65 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:0a:b7:fc

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 ]

landscape-client is not configured, please run landscape-config.

 * Stopping System V initialisation compatibility[74G[ OK ]

 * Starting System V runlevel compatibility[74G[ OK ]

 * Starting automatic crash report generation[74G[ OK ]

 * Starting save kernel messages[74G[ OK ]

 * Starting ACPI daemon[74G[ OK ]

 * Starting regular background program processing daemon[74G[ OK ]

 * Starting deferred execution scheduler[74G[ OK ]

 * Stopping System V runlevel compatibility[74G[ OK ]

 * Starting execute cloud user/final scripts[74G[ OK ]

 * Starting CPU interrupts balancing daemon[74G[ OK ]

root@nova:~# lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 12.10
Release: 12.10
Codename: quantal

root@nova:~# uname -a
Linux nova 3.5.0-17-generic #28-Ubuntu SMP Tue Oct 9 19:31:23 UTC 2012 x86_64 x86_64 x86_64 GNU/Linux

root@nova:~# dpkg -l|egrep "kvm|libvirt|dhcp|dns"
ii dnsmasq-base 2.63-1ubuntu1 amd64 Small caching DNS proxy and DHCP/TFTP server
ii dnsmasq-utils 2.63-1ubuntu1 amd64 Utilities for manipulating DHCP leases
ii dnsutils 1:9.8.1.dfsg.P1-4.2ubuntu3 amd64 Clients provided with BIND
ii isc-dhcp-client 4.2.4-1ubuntu10 amd64 ISC DHCP client
ii isc-dhcp-common 4.2.4-1ubuntu10 amd64 common files used by all the isc-dhcp* packages
ii kvm 1:84+dfsg-0ubuntu16+1.2.0+noroms+0ubuntu2 amd64 dummy transitional package from kvm to qemu-kvm
ii kvm-ipxe 1.0.0+git-3.55f6c88-0ubuntu5 all PXE ROM's for KVM
ii libdns81 1:9.8.1.dfsg.P1-4.2ubuntu3 amd64 DNS Shared Library used by BIND
ii libvirt-bin 0.9.13-0ubuntu12 amd64 programs for the libvirt library
ii libvirt0 0.9.13-0ubuntu12 amd64 library for interfacing with different virtualization systems
ii nova-compute-kvm 2012.2-0ubuntu5 all OpenStack Compute - compute node (KVM)
ii python-libvirt 0.9.13-0ubuntu12 amd64 libvirt Python bindings
ii qemu-kvm 1.2.0+noroms-0ubuntu2 amd64 Full virtualization on supported hardware

root@nova:~# vim /etc/nova/nova.conf
[DEFAULT]
###### LOGS/STATE
#verbose=True
verbose=False

###### AUTHENTICATION
auth_strategy=keystone

###### SCHEDULER
#--compute_scheduler_driver=nova.scheduler.filter_scheduler.FilterScheduler
scheduler_driver=nova.scheduler.simple.SimpleScheduler
###### VOLUMES
volume_group=nova-volumes
volume_name_template=volume-%08x
iscsi_helper=tgtadm
rootwrap_config=/etc/nova/rootwrap.conf
###### DATABASE
sql_connection=mysql://nova:nova@172.31.201.116:3306/nova

###### COMPUTE
libvirt_type=kvm
#libvirt_type=qemu
connection_type=libvirt
instance_name_template=instance-%08x
api_paste_config=/etc/nova/api-paste.ini
allow_resize_to_same_host=True
libvirt_use_virtio_for_bridges=true
start_guests_on_host_boot=true
resume_guests_state_on_host_boot=true

###### APIS

osapi_compute_extension=nova.api.openstack.compute.contrib.standard_extensions
allow_admin_api=true
s3_host=172.31.201.117
cc_host=172.31.201.117

###### RABBITMQ
rabbit_host=172.31.201.117
rabbit_port=5672
rabbit_use_ssl=false
rabbit_userid="guest"
rabbit_virtual_host="/"

###### GLANCE
image_service=nova.image.glance.GlanceImageService
glance_api_servers=172.31.201.110:9292

###### NETWORK
network_manager=nova.network.manager.FlatDHCPManager
force_dhcp_release=True
dhcpbridge_flagfile=/etc/nova/nova.conf
dhcpbridge=/usr/bin/nova-dhcpbridge
firewall_driver=nova.virt.libvirt.firewall.IptablesFirewallDriver
public_interface=eth0
flat_interface=eth1
flat_network_bridge=br100
fixed_range=10.200.200.0/24
multi_host=True
flat_injected=True
#my_ip=172.31.201.117
###### NOVNC CONSOLE
novnc_enabled=true
novncproxy_base_url= http://172.31.201.117:6080/vnc_auto.html
vncserver_proxyclient_address=172.31.201.117
vncserver_listen=172.31.201.117

########Nova
logdir=/var/log/nova
state_path=/var/lib/nova
lock_path=/var/lock/nova

#####MISC
use_deprecated_auth=false
root_helper=sudo nova-rootwrap

Revision history for this message
Robie Basak (racb) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better.

This sounds like either a local misconfiguration in OpenStack or a bug in OpenStack. Although it could be a libvirt issue, with the limited information we have I don't see how we can justify that at this time. So reassigning to nova.

affects: libvirt (Ubuntu) → nova (Ubuntu)
Changed in nova (Ubuntu):
status: New → Incomplete
Revision history for this message
Thiago Martins (martinx) wrote :

Hi!

 I followed this guide: http://docs.openstack.org/folsom/basic-install/content/basic-install_intro.html more than 10 times.

 Always I hit this problem:

----------
cloud-init start-local running: Thu, 03 Jan 2013 04:20:52 +0000. up 8.53 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:83:06:4f

route_info failed

Waiting for network configuration...

Waiting up to 60 more seconds for network configuration...

Booting system without full network configuration...
----------

 So, no network connectivity within my Instance.

 How can I debug it?

Tks,
Thiago

Revision history for this message
Chuck Short (zulcss) wrote :

can you attach your nova-network.log and nova-compute.log.

Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for nova (Ubuntu) because there has been no activity for 60 days.]

Changed in nova (Ubuntu):
status: Incomplete → Expired
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.