<div dir="ltr"><div><div><div><div><div>Hi,<br><br></div>I have got to the point where I am trying to launch a virtual machine as per <a href="http://docs.openstack.org/folsom/openstack-compute/install/yum/content/running-an-instance.html" target="_blank">http://docs.openstack.org/folsom/openstack-compute/install/yum/content/running-an-instance.html</a><br>
<br></div>The boot command completes but it seems some key element of networking is failing.<br></div><div>Does anyone have suggestions on how to trouble shoot this issue further?<br></div><div><br>$ nova boot --flavor 2 --image 9ed7b2c4-f296-4fd0-9ffa-026231947a09 --key_name mykey --security_group default cirros<br>
+-------------------------------------+--------------------------------------+<br>| Property | Value |<br>+-------------------------------------+--------------------------------------+<br>
| OS-DCF:diskConfig | MANUAL |<br>| OS-EXT-SRV-ATTR:host | None |<br>| OS-EXT-SRV-ATTR:hypervisor_hostname | None |<br>
| OS-EXT-SRV-ATTR:instance_name | instance-00000006 |<br>| OS-EXT-STS:power_state | 0 |<br>| OS-EXT-STS:task_state | scheduling |<br>
| OS-EXT-STS:vm_state | building |<br>| accessIPv4 | |<br>| accessIPv6 | |<br>
| adminPass | ASyz54u26TGK |<br>| config_drive | |<br>| created | 2013-07-30T22:14:32Z |<br>
| flavor | m1.small |<br>| hostId | |<br>| id | fc0c5515-9d30-4263-87ea-0f912c0fc7c7 |<br>
| image | cirros-0.3.0-x86_64 |<br>| key_name | mykey |<br>| metadata | {} |<br>
| name | cirros |<br>| progress | 0 |<br>| security_groups | [{u'name': u'default'}] |<br>
| status | BUILD |<br>| tenant_id | f037ea1bab6d4dc08b880c5fdea29fb5 |<br>| updated | 2013-07-30T22:14:32Z |<br>
| user_id | a66355f1760448989e63dc54e853674f |<br>+-------------------------------------+--------------------------------------+<br><br></div>But I notice that no IPV4 address has been assigned<br>
<br></div>If do nova lists during the boot process I see the following<br><br>$ nova list<br>+--------------------------------------+--------+--------+----------+<br>| ID | Name | Status | Networks |<br>
+--------------------------------------+--------+--------+----------+<br>| fc0c5515-9d30-4263-87ea-0f912c0fc7c7 | cirros | BUILD | |<br>+--------------------------------------+--------+--------+----------+<br>$ nova list<br>
+--------------------------------------+--------+--------+-----------------------+<br>| ID | Name | Status | Networks |<br>+--------------------------------------+--------+--------+-----------------------+<br>
| fc0c5515-9d30-4263-87ea-0f912c0fc7c7 | cirros | BUILD | private=192.168.100.2 |<br>+--------------------------------------+--------+--------+-----------------------+<br>$ nova list<br>+--------------------------------------+--------+--------+-----------------------+<br>
| ID | Name | Status | Networks |<br>+--------------------------------------+--------+--------+-----------------------+<br>| fc0c5515-9d30-4263-87ea-0f912c0fc7c7 | cirros | ERROR | private=192.168.100.2 |<br>
+--------------------------------------+--------+--------+-----------------------+<br><br></div>And if I wait some time and then repeat the nova list it will change to<br><div>$ nova list<br>+--------------------------------------+--------+--------+----------+<br>
| ID | Name | Status | Networks |<br>+--------------------------------------+--------+--------+----------+<br>| fc0c5515-9d30-4263-87ea-0f912c0fc7c7 | cirros | ERROR | |<br>+--------------------------------------+--------+--------+----------+<br>
<br></div><div>The process does not seem to be getting as far as attempting to boot the image<br><br>$ nova console-log fc0c5515-9d30-4263-87ea-0f912c0fc7c7<br>ERROR: The resource could not be found. (HTTP 404) (Request-ID: req-b10876a4-9193-4158-829e-3454e80c706f)<br>
</div><div><br></div><div>There doesn't seem to be any obvious errors in /var/log/nova/network.log. <a href="http://www.cms.waikato.ac.nz/%7Eclintd/nova-network.log" target="_blank">http://www.cms.waikato.ac.nz/~clintd/nova-network.log</a><br>
<br></div><div>And all nova related services appear to be running<br></div><div>]# nova-manage service list<br>Binary Host Zone Status State Updated_At<br>nova-volume prancer nova enabled :-) 2013-07-30 23:14:22<br>
nova-scheduler prancer nova enabled :-) 2013-07-30 23:14:28<br>nova-cert prancer nova enabled :-) 2013-07-30 23:14:25<br>
nova-compute prancer nova enabled :-) 2013-07-30 23:14:21<br>nova-network prancer nova enabled :-) 2013-07-30 23:14:27<br>
nova-console prancer nova enabled :-) 2013-07-30 23:14:26<br>nova-consoleauth prancer nova enabled :-) 2013-07-30 23:14:23<br>
<br># ip a<br>1: lo: <LOOPBACK,UP,LOWER_UP> mtu 16436 qdisc noqueue state UNKNOWN <br> link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00<br> inet <a href="http://127.0.0.1/8" target="_blank">127.0.0.1/8</a> scope host lo<br>
inet <a href="http://169.254.169.254/32" target="_blank">169.254.169.254/32</a> scope link lo<br>2: em1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP qlen 1000<br> link/ether 00:24:e8:fe:0e:8a brd ff:ff:ff:ff:ff:ff<br>
inet <a href="http://130.217.218.18/16" target="_blank">130.217.218.18/16</a> brd 130.217.255.255 scope global em1<br>3: em2: <NO-CARRIER,BROADCAST,MULTICAST,PROMISC,UP> mtu 1500 qdisc mq state DOWN qlen 1000<br>
link/ether 00:24:e8:fe:0e:8b brd ff:ff:ff:ff:ff:ff<br>
5: br100: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UNKNOWN <br> link/ether 00:24:e8:fe:0e:8b brd ff:ff:ff:ff:ff:ff<br> inet <a href="http://192.168.100.1/24" target="_blank">192.168.100.1/24</a> brd 192.168.100.255 scope global br100<br>
inet <a href="http://192.168.206.130/24" target="_blank">192.168.206.130/24</a> brd 192.168.206.255 scope global br100<br>8: virbr0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UNKNOWN <br> link/ether 52:54:00:83:81:d1 brd ff:ff:ff:ff:ff:ff<br>
inet <a href="http://192.168.122.1/24" target="_blank">192.168.122.1/24</a> brd 192.168.122.255 scope global virbr0<br>9: virbr0-nic: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN qlen 500<br> link/ether 52:54:00:83:81:d1 brd ff:ff:ff:ff:ff:ff<br>
</div><div><br>I am also seeing the following in /var/log messages. Could it be related to the problem?<br> <br></div><div>Jul 31 10:46:55 prancer dnsmasq[17941]: read /etc/hosts - 2 addresses<br>Jul 31 10:46:55 prancer dnsmasq[17941]: read /var/lib/nova/networks/nova-br100.conf<br>
Jul 31 10:48:22 prancer dnsmasq[17941]: read /etc/hosts - 2 addresses<br>Jul 31 10:48:22 prancer dnsmasq[17941]: read /var/lib/nova/networks/nova-br100.conf<br>Jul 31 10:50:29 prancer dnsmasq[17941]: read /etc/hosts - 2 addresses<br>
Jul 31 10:50:29 prancer dnsmasq[17941]: read /var/lib/nova/networks/nova-br100.conf<br>Jul 31 10:50:31 prancer dnsmasq[17941]: read /etc/hosts - 2 addresses<br>Jul 31 10:50:31 prancer dnsmasq[17941]: read /var/lib/nova/networks/nova-br100.conf<br>
Jul 31 10:50:32 prancer dnsmasq-dhcp[17941]: DHCPRELEASE(br100) 192.168.100.2 fa:16:3e:7f:0f:96 unknown lease<br><br></div># cat /etc/nova/nova.conf<br>[DEFAULT]<br><br># LOGS/STATE<br>verbose=True<br>logdir=/var/log/nova<br>
state_path=/var/lib/nova<br>lock_path=/var/lock/nova<br>rootwrap_config=/etc/nova/<div>rootwrap.conf<br><br># SCHEDULER<br>compute_scheduler_driver=nova.scheduler.filter_scheduler.FilterScheduler<br><br># VOLUMES<br>volume_driver=nova.volume.driver.ISCSIDriver<br>
volume_group=nova-volumes<br>volume_name_template=volume-%08x<br>iscsi_helper=tgtadm<br><br># DATABASE<br>sql_connection=mysql://<a href="http://nova:0pen5tack-nova@192.168.206.130/nova" target="_blank">nova:0pen5tack-nova@192.168.206.130/nova</a><br>
<br># COMPUTE<br>libvirt_type=kvm<br>compute_driver=libvirt.LibvirtDriver<br>instance_name_template=instance-%08x<br>api_paste_config=/etc/nova/api-paste.ini<br><br># COMPUTE/APIS: if you have separate configs for separate services<br>
# this flag is required for both nova-api and nova-compute<br>allow_resize_to_same_host=True<br><br># APIS<br>osapi_compute_extension=nova.api.openstack.compute.contrib.standard_extensions<br>ec2_dmz_host=192.168.206.130<br>
s3_host=192.168.206.130<br><br># Qpid<br>rpc_backend=nova.rpc.impl_qpid<br>qpid_hostname=192.168.206.130<br><br># GLANCE<br>image_service=nova.image.glance.GlanceImageService<br>glance_api_servers=<a href="http://192.168.206.130:9292" target="_blank">192.168.206.130:9292</a><br>
<br># NETWORK<br>network_manager=nova.network.manager.FlatDHCPManager<br>dhcpbridge=/usr/bin/nova-dhcpbridge<br>force_dhcp_release=True<br>dhcpbridge_flagfile=/etc/nova/nova.conf<br>firewall_driver=nova.virt.libvirt.firewall.IptablesFirewallDriver<br>
# Change my_ip to match each host<br>my_ip=192.168.206.130<br>public_interface=em2<br>vlan_interface=em2<br>flat_network_bridge=br100<br>flat_interface=em2<br>fixed_range=<a href="http://192.168.100.0/24" target="_blank">192.168.100.0/24</a><br>
<br># NOVNC CONSOLE<br>novncproxy_base_url=<a href="http://192.168.206.130:6080/vnc_auto.html" target="_blank">http://192.168.206.130:6080/vnc_auto.html</a><br># Change vncserver_proxyclient_address and vncserver_listen to match each compute host<br>
vncserver_proxyclient_address=192.168.206.130<br>vncserver_listen=192.168.206.130<br><br># AUTHENTICATION<br>auth_strategy=keystone<br>[keystone_authtoken]<br>auth_host = 127.0.0.1<br>auth_port = 35357<br>auth_protocol = http<br>
admin_tenant_name = service<br>admin_user = nova<br>admin_password = nova<br>signing_dirname = /tmp/keystone-signing-nova<br><br><br><div>Thanks for any advice you are willing to share :)</div></div></div>