My new instance gets stuck in spawning state, nova-network problem?

asked 2014-12-10 08:00:39 -0600

Tam Nguyen gravatar image

Dear experts,

I'm a newbie in OpenStack. This week I did configure Openstack icehouse on Amazon web service (AWS) using EC2. Unfortunately, It does not work as my expectation. After configuring according to installation guideline on OpenStack homepage, I tried to launch a new instance. However it got stuck at "spawning" state and I even could not delete it. Could you guys please help me to troubleshooting this?

My cloud

I create 5 EC2 nodes on AWS to deploy as the following architecture, All nodes is Ubuntu14.04, https://lh3.googleusercontent.com/ihGFJBAbceWXHHv343oAMVeYopkj2hvF-4gViBSjo-EAc3gQeFiI1Ye2t_3zGmq-IeKzBA=w973-h511 (image description)

Condition

I did some tests but I still not figure out the root cause. First, I check Keystone node and its seemingly OK https://lh5.googleusercontent.com/kA3B6LDwA0oETmrlhO8WlzBT0jlGULGj3OwGKB4j99LTEimaQtq2871DWt0aWu0DVJ3et8KDqFo=w990-h511 (image description) https://lh5.googleusercontent.com/9H9qnIApKLAp-GvoXUmONv2aF5WLLkb8w9Y9TBYWwnb1iB3F2iO0WnP4eB-FXyjm4UD-qqYIbYM=w990-h511 (image description)

Here is Glance node: https://lh5.googleusercontent.com/98aH-a4Eit9ZzYoyg8b1tyM9qpf3UUZjkv8gflZHnTqG5nvIyI-fX75gukBsNCMh7ZLDIi3YAfw=w990-h511 (image description)

And Horizon dashboard: https://lh5.googleusercontent.com/nv6_oUF21ZAMxzjRP2Jq8nRWxvxA8r__rMvuwhe7Mjiqcf8cEpNorBtLWzIEj7ROiNlfVpPM9T8=w990-h511 (image description)

Controller node:

https://lh5.googleusercontent.com/GghE3Fr6YggLF8xWzloH00IuikmeX6moIH4NqP5nKIth4C4OV_Jf8OEuPtD89lI2VAl1Yfuxbuo=w990-h511 (image description) https://lh5.googleusercontent.com/rF59-doMn808ikQeqfAoOyYaKXOP2x9m6z503sIoaiK7xQH6ddLwhMd0BOW2v1Z7rjtFAB7NhfU=w990-h511 (image description) https://lh5.googleusercontent.com/TxcSSSTDoY-aZKST_2Dq9EV6nliE5B1pGzI51dEHS4IHScL1dPpJpzK3EUueMcFDXC6AurDoeYY=w990-h511 (image description)

Compute node: I checked nova-compute.log file and I found some such errors as the following: https://lh5.googleusercontent.com/YIsBX2AOrttLeIlsW9uhXILgL3TiVhxR1-pjQmXQpWT45ZfLL0HALlmU-6B4teASnh2AamkEAzQ=w990-h511 (image description)

It's said that MySQL server on Controller node is non-accessible by default setting. This caused the second error. I changed MySQL configuration by adding "bin-address = <controller ip="">" and found that the second error disappeared. However the first error log still occurred. I think my configuration regarding network at compute node is incorrect. How far could I go to check this?

There are nova.conf files

Compute node:

[DEFAULT]
dhcpbridge_flagfile=/etc/nova/nova.conf
dhcpbridge=/usr/bin/nova-dhcpbridge
logdir=/var/log/nova
state_path=/var/lib/nova
lock_path=/var/lock/nova
force_dhcp_release=True
iscsi_helper=tgtadm
libvirt_use_virtio_for_bridges=True
connection_type=libvirt
root_helper=sudo nova-rootwrap /etc/nova/rootwrap.conf
verbose=True
ec2_private_dns_show_ip=True
api_paste_config=/etc/nova/api-paste.ini
volumes_path=/var/lib/nova/volumes
enabled_apis=ec2,osapi_compute,metadata

# lacking
libvirt_type=qemu

# Rabbit MQ
rpc_backend = rabbit
rabbit_host = 172.31.25.119
rabbit_password = openstack

# Remote console access
my_ip = 172.31.19.49
vnc_enabled = True
vncserver_listen = 0.0.0.0
vncserver_proxyclient_address = 172.31.19.49
novncproxy_base_url = http://172.31.25.119:6080/vnc_auto.html

# Image service
glance_host = 172.31.28.53

# Authentican
auth_strategy = keystone

# Legacy network
network_api_class = nova.network.api.API
security_group_api = nova
firewall_driver = nova.virt.libvirt.firewall.IptablesFirewallDriver
network_manager = nova.network.manager.FlatDHCPManager
network_size = 254
allow_same_net_traffic = False
multi_host = True
send_arp_for_ha = True
share_dhcp_address = True
force_dhcp_release = True
flat_network_bridge = br100
#flat_interface_bridge = br100
flat_interface = eth0
public_interface = eth0
#lacking
auto_assign_floating_ip=True

[database]
# The SQLAlchemy connection string used to connect to the database
connection = mysql://nova:openstack@172.31.25.119/nova

[keystone_authtoken]
auth_uri = http://172.31.22.38:5000
auth_host = 172.31.22.38
auth_port = 35357
auth_protocol = http
admin_tenant_name = service1
admin_user = nova
admin_password = openstack

Controller node:

[DEFAULT]
dhcpbridge_flagfile=/etc/nova/nova.conf
dhcpbridge=/usr/bin/nova-dhcpbridge
logdir=/var/log/nova
state_path=/var/lib/nova
lock_path=/var/lock/nova
force_dhcp_release=True
iscsi_helper=tgtadm
libvirt_use_virtio_for_bridges ...
(more)
edit retag flag offensive close merge delete

Comments

can you provide some logs?

rishi gravatar imagerishi ( 2014-12-12 00:34:14 -0600 )edit