Open Stack

You can see the IP in dashboard is because neutron-server already picked the IP from database for your instance.

After IP address been picked, neutron-server will send the IP address to neutron-dhcp-agent.
If you checked the host which is running neutron-dhcp-agent, you should see a process "dnsmasq" is running to serve your neutron network.
You might be interested at the parameter "dhcp-hostfile" for "dnsmasq".
This file contains your instances' MAC addresses and the corresponding IP address  "dnsmasq" (dhcp server) would distribute for your instances.

If the DHCP server (the dnsmasq process) is working appropriate, then after your instances start, the instance will send out DHCP request to DHCP server.
There should be logs for these DHCP request and DHCP ACK in the syslog ( or /var/log/messages ?)

If the dhcp server not receive the DHCP request, you might check the neutron-openvswitch-agent (or other agent if you're not using OVS) status on two node: Compute node and the node running neutron-dhcp-agent. If you're using VLAN, check your switch's configurations.

If the dhcp server do received DHCP request and responded with the right IP, and you're working under gre/vxlan, then maybe you should enlarge your MTU for your physical network ports.

Thanks.
-chen


From: Chetan Bali [mailto:chetan.bali at aricent.com]
Sent: Thursday, January 22, 2015 12:26 PM
To: Li, Chen; openstack at lists.openstack.org
Subject: RE: unable to launch instance on icehouse 3 node setup

Hi Li,

Thanks for the response. This really resolved my issue of launching the instance.

One issue I am seeing now is my instance is showing the IP - 123.0.0.14 [ demo subnet ] in dashboard but I am not able to see the IP address on eth0 of guest VM.

I tried manually getting the IP using dhclient but seems like dhclient is not installed in cirros tiny flavour image.

Can you help resolve this issue?

Thanks
Chetan Bali

From: Li, Chen [mailto:chen.li at intel.com]
Sent: 22 January 2015 08:04
To: Chetan Bali; openstack at lists.openstack.org<mailto:openstack at lists.openstack.org>
Subject: RE: unable to launch instance on icehouse 3 node setup

Hi,

I don't know the error in dashboard.
But this looks like nova can't create directory:
OSError: [Errno 13] Permission denied: '/var/lib/nova/instances/6bde1525-5c72-4d5d-815e-1205ed0e6bde'

Check yourdirectory :
        ll /var/lib/nova/instances/
If it looks like:
        drwxr-xr-x 6 root root     4096 Jan  6 14:44 ./
Edit it:
        Chown -R nova:nova /var/lib/nova/instances/

Thanks.
-chen

From: Chetan Bali [mailto:chetan.bali at aricent.com]
Sent: Thursday, January 22, 2015 10:17 AM
To: openstack at lists.openstack.org<mailto:openstack at lists.openstack.org>
Subject: [Openstack] unable to launch instance on icehouse 3 node setup

Hi,

I have a setup with 3 node architecture with [ 1 controller + 1 compute + 1 network node ].

My services are in running state for all nova and neutron.

When I try to launch a instance from demo user, I am getting "no valid host found" error in dashboard.

While seeing nova-compute.log in compute node, I see following errors:





2015-01-22 07:31:36.963 10485 AUDIT nova.compute.manager [req-d75088cb-bb2d-4249-baba-e4fd5763675c d1d5dde0e1074187a8de213989099cb0 9626b042b482469486fa7103c35d1203] [instance: 6bde1525-5c72-4d5d-815e-1205ed0e6bde] Starting instance...
2015-01-22 07:31:37.106 10485 AUDIT nova.compute.claims [req-d75088cb-bb2d-4249-baba-e4fd5763675c d1d5dde0e1074187a8de213989099cb0 9626b042b482469486fa7103c35d1203] [instance: 6bde1525-5c72-4d5d-815e-1205ed0e6bde] Attempting claim: memory 512 MB, disk 1 GB, VCPUs 1
2015-01-22 07:31:37.106 10485 AUDIT nova.compute.claims [req-d75088cb-bb2d-4249-baba-e4fd5763675c d1d5dde0e1074187a8de213989099cb0 9626b042b482469486fa7103c35d1203] [instance: 6bde1525-5c72-4d5d-815e-1205ed0e6bde] Total memory: 11935 MB, used: 1024.00 MB
2015-01-22 07:31:37.107 10485 AUDIT nova.compute.claims [req-d75088cb-bb2d-4249-baba-e4fd5763675c d1d5dde0e1074187a8de213989099cb0 9626b042b482469486fa7103c35d1203] [instance: 6bde1525-5c72-4d5d-815e-1205ed0e6bde] memory limit: 17902.50 MB, free: 16878.50 MB
2015-01-22 07:31:37.107 10485 AUDIT nova.compute.claims [req-d75088cb-bb2d-4249-baba-e4fd5763675c d1d5dde0e1074187a8de213989099cb0 9626b042b482469486fa7103c35d1203] [instance: 6bde1525-5c72-4d5d-815e-1205ed0e6bde] Total disk: 905 GB, used: 1.00 GB
2015-01-22 07:31:37.107 10485 AUDIT nova.compute.claims [req-d75088cb-bb2d-4249-baba-e4fd5763675c d1d5dde0e1074187a8de213989099cb0 9626b042b482469486fa7103c35d1203] [instance: 6bde1525-5c72-4d5d-815e-1205ed0e6bde] disk limit not specified, defaulting to unlimited
2015-01-22 07:31:37.107 10485 AUDIT nova.compute.claims [req-d75088cb-bb2d-4249-baba-e4fd5763675c d1d5dde0e1074187a8de213989099cb0 9626b042b482469486fa7103c35d1203] [instance: 6bde1525-5c72-4d5d-815e-1205ed0e6bde] Total CPUs: 4 VCPUs, used: 1.00 VCPUs
2015-01-22 07:31:37.107 10485 AUDIT nova.compute.claims [req-d75088cb-bb2d-4249-baba-e4fd5763675c d1d5dde0e1074187a8de213989099cb0 9626b042b482469486fa7103c35d1203] [instance: 6bde1525-5c72-4d5d-815e-1205ed0e6bde] CPUs limit not specified, defaulting to unlimited
2015-01-22 07:31:37.107 10485 AUDIT nova.compute.claims [req-d75088cb-bb2d-4249-baba-e4fd5763675c d1d5dde0e1074187a8de213989099cb0 9626b042b482469486fa7103c35d1203] [instance: 6bde1525-5c72-4d5d-815e-1205ed0e6bde] Claim successful
2015-01-22 07:31:38.040 10485 ERROR nova.compute.manager [req-d75088cb-bb2d-4249-baba-e4fd5763675c d1d5dde0e1074187a8de213989099cb0 9626b042b482469486fa7103c35d1203] [instance: 6bde1525-5c72-4d5d-815e-1205ed0e6bde] Instance failed to spawn
2015-01-22 07:31:38.040 10485 TRACE nova.compute.manager [instance: 6bde1525-5c72-4d5d-815e-1205ed0e6bde] Traceback (most recent call last):
2015-01-22 07:31:38.040 10485 TRACE nova.compute.manager [instance: 6bde1525-5c72-4d5d-815e-1205ed0e6bde]   File "/usr/lib/python2.7/dist-packages/nova/compute/manager.py", line 1720, in _spawn
2015-01-22 07:31:38.040 10485 TRACE nova.compute.manager [instance: 6bde1525-5c72-4d5d-815e-1205ed0e6bde]     block_device_info)
2015-01-22 07:31:38.040 10485 TRACE nova.compute.manager [instance: 6bde1525-5c72-4d5d-815e-1205ed0e6bde]   File "/usr/lib/python2.7/dist-packages/nova/virt/libvirt/driver.py", line 2246, in spawn
2015-01-22 07:31:38.040 10485 TRACE nova.compute.manager [instance: 6bde1525-5c72-4d5d-815e-1205ed0e6bde]     admin_pass=admin_password)
2015-01-22 07:31:38.040 10485 TRACE nova.compute.manager [instance: 6bde1525-5c72-4d5d-815e-1205ed0e6bde]   File "/usr/lib/python2.7/dist-packages/nova/virt/libvirt/driver.py", line 2560, in _create_image
2015-01-22 07:31:38.040 10485 TRACE nova.compute.manager [instance: 6bde1525-5c72-4d5d-815e-1205ed0e6bde]     fileutils.ensure_tree(libvirt_utils.get_instance_path(instance))
2015-01-22 07:31:38.040 10485 TRACE nova.compute.manager [instance: 6bde1525-5c72-4d5d-815e-1205ed0e6bde]   File "/usr/lib/python2.7/dist-packages/nova/openstack/common/fileutils.py", line 37, in ensure_tree
2015-01-22 07:31:38.040 10485 TRACE nova.compute.manager [instance: 6bde1525-5c72-4d5d-815e-1205ed0e6bde]     os.makedirs(path)
2015-01-22 07:31:38.040 10485 TRACE nova.compute.manager [instance: 6bde1525-5c72-4d5d-815e-1205ed0e6bde]   File "/usr/lib/python2.7/os.py", line 157, in makedirs
2015-01-22 07:31:38.040 10485 TRACE nova.compute.manager [instance: 6bde1525-5c72-4d5d-815e-1205ed0e6bde]     mkdir(name, mode)
2015-01-22 07:31:38.040 10485 TRACE nova.compute.manager [instance: 6bde1525-5c72-4d5d-815e-1205ed0e6bde] OSError: [Errno 13] Permission denied: '/var/lib/nova/instances/6bde1525-5c72-4d5d-815e-1205ed0e6bde'


Thanks
Chetan Bali
"DISCLAIMER: This message is proprietary to Aricent and is intended solely for the use of the individual to whom it is addressed. It may contain privileged or confidential information and should not be circulated or used for any purpose other than for what it is intended. If you have received this message in error, please notify the originator immediately. If you are not the intended recipient, you are notified that you are strictly prohibited from using, copying, altering, or disclosing the contents of this message. Aricent accepts no responsibility for loss or damage arising from the use of the information transmitted by this email including damage from virus."
"DISCLAIMER: This message is proprietary to Aricent and is intended solely for the use of the individual to whom it is addressed. It may contain privileged or confidential information and should not be circulated or used for any purpose other than for what it is intended. If you have received this message in error, please notify the originator immediately. If you are not the intended recipient, you are notified that you are strictly prohibited from using, copying, altering, or disclosing the contents of this message. Aricent accepts no responsibility for loss or damage arising from the use of the information transmitted by this email including damage from virus."
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack/attachments/20150122/ca117349/attachment.html>