Instances has no fixed ip allocated and stay in pending state
Hi all,
I have configured a two-node environment with one contrllor node (OpenstackServer) runs all the nova services including nova-compute and one compute node (openstack2) that runs only nova-compute. Both nodes are running Diablo based on Ubuntu 11.10 server. For now, I can successfully run an instance on the controller node, and the compute node is in :-) state when I run "sudo nova-manage service list" on the controller node. But when I spawn an instance on the compute node, the instance stay in pending state and has no ip allcated.
On controller node, I have network interfaces as below:
auto lo
iface lo inet loopback
auto eth0
iface eth0 inet static
address 10.201.194.101
netmask 255.255.255.0
broadcast 10.201.194.127
gateway 10.201.194.126
dns-nameservers 8.8.8.8
auto eth1
iface eth1 inet static
address 192.168.3.1
netmask 255.255.255.0
network 192.168.3.0
broadcast 192.168.3.255
br100 Link encap:Ethernet HWaddr 00:26:b9:8d:a5:37
inet addr:172.16.0.3 Bcast:172.16.0.255 Mask:255.255.255.0
inet6 addr: fe80::226:
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:528469 errors:0 dropped:0 overruns:0 frame:0
TX packets:1502 errors:0 dropped:0 overruns:0 carrier:0
RX bytes:25478029 (25.4 MB) TX bytes:136029 (136.0 KB)
eth0 Link encap:Ethernet HWaddr 00:26:b9:8d:a5:36
inet addr:10.201.194.101 Bcast:10.
inet6 addr: fe80::226:
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:3710355 errors:0 dropped:0 overruns:0 frame:0
TX packets:20689912 errors:0 dropped:0 overruns:0 carrier:0
RX bytes:443067374 (443.0 MB) TX bytes:6690527683 (6.6 GB)
eth1 Link encap:Ethernet HWaddr 00:26:b9:8d:a5:37
inet6 addr: fe80::226:
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:556611 errors:0 dropped:0 overruns:0 frame:0
TX packets:3310 errors:0 dropped:0 overruns:0 carrier:0
RX bytes:36944751 (36.9 MB) TX bytes:376678 (376.6 KB)
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:1444405 errors:0 dropped:0 overruns:0 frame:0
TX packets:1444405 errors:0 dropped:0 overruns:0 carrier:0
RX bytes:1125911682 (1.1 GB) TX bytes:1125911682 (1.1 GB)
virbr0 Link encap:Ethernet HWaddr 42:9e:88:46:ac:01
inet addr:192.168.122.1 Bcast:192.
UP BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)
vnet0 Link encap:Ethernet HWaddr fe:16:3e:1c:2b:0e
inet6 addr: fe80::fc16:
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:498 errors:0 dropped:0 overruns:0 frame:0
TX packets:623 errors:0 dropped:0 overruns:0 carrier:0
RX bytes:151152 (151.1 KB) TX bytes:184020 (184.0 KB)
And the network interfaces of the compute node:
auto lo
iface lo inet loopback
auto eth0
iface eth0 inet static
address 10.201.194.102
netmask 255.255.255.0
broadcast 10.201.194.127
gateway 10.201.194.126
dns-nameservers 8.8.8.8
auto eth1
iface eth1 inet static
address 192.168.3.4
netmask 255.255.255.0
network 192.168.3.0
broadcast 192.168.3.255
eth0 Link encap:Ethernet HWaddr 00:26:b9:8d:7b:46
inet addr:10.201.194.102 Bcast:10.
inet6 addr: fe80::226:
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:721192 errors:0 dropped:0 overruns:0 frame:0
TX packets:3299126 errors:0 dropped:0 overruns:0 carrier:0
RX bytes:160267210 (160.2 MB) TX bytes:1107300583 (1.1 GB)
eth1 Link encap:Ethernet HWaddr 00:26:b9:8d:7b:47
inet addr:192.168.3.4 Bcast:192.168.3.255 Mask:255.255.255.0
inet6 addr: fe80::226:
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:76258 errors:0 dropped:0 overruns:0 frame:0
TX packets:203 errors:0 dropped:0 overruns:0 carrier:0
RX bytes:5011394 (5.0 MB) TX bytes:18222 (18.2 KB)
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:301 errors:0 dropped:0 overruns:0 frame:0
TX packets:301 errors:0 dropped:0 overruns:0 carrier:0
RX bytes:27872 (27.8 KB) TX bytes:27872 (27.8 KB)
virbr0 Link encap:Ethernet HWaddr 96:58:5f:ef:60:ce
inet addr:192.168.122.1 Bcast:192.
UP BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)
The nova.conf of both controller and compute node:
--verbose=true
--allow_
--use_deprecate
#logging and other administrative
--dhcpbridge_
--dhcpbridge=
--logdir=
--state_
--lock_
#network
--network_
--public_
--flat_
--flat_
--force_
--fixed_
--flat_
--routing_source_ip = 10.201.194.101
--multi_host=T
--network_size=255
--flat_
--network_
--my_ip=
--api_paste_
#vnc
--vncproxy_url=http://
--vncproxy_
#scheduler
--scheduler_
#glance
--image_
--glance_
#--glance_
#rabbit
--rabbit_
#nova database
--sql_connectio
#volumes
--volume_
--aoe_eth_dev=eth0
--iscsi_
The setting of network seem to be fine:
id IPv4 IPv6 start address DNS1 DNS2 VlanID project uuid
1 172.16.0.0/24 None 172.16.0.2 8.8.8.8 None None None None
And following are the log files:
nova-network.log:
2012-04-05 16:00:15,501 DEBUG nova.rpc [-] received {u'_context_roles': [u'Admin', u'Admin'], u'_msg_id': u'3093b09f9bdd4
2012-04-05 16:00:15,502 DEBUG nova.rpc [-] unpacked context: {'user_id': u'adminUser', 'roles': [u'Admin', u'Admin'], 'timestamp': u'2012-
2012-04-05 16:00:15,502 DEBUG nova.network.
2012-04-05 16:00:15,503 DEBUG nova.network.
2012-04-05 16:00:15,554 DEBUG nova.rpc [-] Making asynchronous call on network.openstack3 ... from (pid=1042) multicall /usr/lib/
2012-04-05 16:00:15,555 DEBUG nova.rpc [-] MSG_ID is 686f963f85db487
nova-compute.log of compute node:
2012-04-05 16:00:14,418 DEBUG nova.rpc [-] received {u'_context_roles': [u'Admin', u'Admin'], u'_context_
2012-04-05 16:00:14,419 DEBUG nova.rpc [-] unpacked context: {'user_id': u'adminUser', 'roles': [u'Admin', u'Admin'], 'timestamp': u'2012-
2012-04-05 16:00:15,350 AUDIT nova.compute.
2012-04-05 16:00:15,483 DEBUG nova.rpc [-] Making asynchronous call on network ... from (pid=1905) multicall /usr/lib/
2012-04-05 16:00:15,483 DEBUG nova.rpc [-] MSG content: {'args': {'vpn': False, 'requested_
2012-04-05 16:00:15,484 DEBUG nova.rpc [-] MSG_ID is 3093b09f9bdd4b9
2012-04-05 16:00:15,484 DEBUG nova.rpc [-] Pool creating new connection from (pid=1905) create /usr/lib/
2012-04-05 16:00:15,489 INFO nova.rpc [-] Connected to AMQP server on 10.201.194.101:5672
2012-04-05 16:00:40,318 INFO nova.compute.
2012-04-05 16:01:40,328 INFO nova.compute.
It seems like nova-network cannot get to the network_info step because the fixed ip does not be allocated. Can anyone help or do you need any further information? Thanks in advance.
Gary
Question information
- Language:
- English Edit question
- Status:
- Solved
- Assignee:
- No assignee Edit question
- Solved by:
- yong sheng gong
- Solved:
- Last query:
- Last reply: