Multi node deploy: instance spawning failure
Hello,
I have deployed latest nova on 2 host machines, one for controller(
Problem is, as I hit run instance from the controller node, following compute error occurs on the compute node.
nova-compute, nova-scheduler service was successfully added on the service table and euca-describe-
root@cloud02:
cloud02 nova-scheduler enabled :-) 2011-04-05 09:01:01
cloud02 nova-network enabled :-) 2011-04-05 09:01:01
cloud01 nova-scheduler enabled :-) 2011-04-05 08:59:23
cloud01 nova-compute enabled :-) 2011-04-05 08:59:17
root@cloud02:
RESERVATION r-etss4atr NOVAADMPRJ default
INSTANCE i-00000002 ami-0640184b 10.0.0.3 10.0.0.3 failed to spawn novaadm (NOVAADMPRJ, cloud01) 0 m1.small 2011-04-
=======
2011-04-05 17:48:41,923 AUDIT nova.compute.
2011-04-05 17:48:42,018 DEBUG nova.rpc [-] Making asynchronous call on network.cloud02 ... from (pid=4290) call /root/openstack
2011-04-05 17:48:42,019 DEBUG nova.rpc [-] MSG_ID is 1d0b70e00fc94c1
2011-04-05 17:48:42,458 DEBUG nova.virt.
2011-04-05 17:48:42,531 DEBUG nova.virt.
2011-04-05 17:48:42,582 INFO nova [-] called setup_basic_
2011-04-05 17:48:42,582 INFO nova [-] ensuring static filters
2011-04-05 17:48:42,648 DEBUG nova.utils [-] Attempting to grab semaphore "iptables" for method "apply"... from (pid=4290) inner /root/openstack
2011-04-05 17:48:42,648 DEBUG nova.utils [-] Attempting to grab file lock "iptables" for method "apply"... from (pid=4290) inner /root/openstack
2011-04-05 17:48:42,653 DEBUG nova.utils [-] Running cmd (subprocess): sudo iptables-save -t filter from (pid=4290) execute /root/openstack
2011-04-05 17:48:42,665 DEBUG nova.utils [-] Running cmd (subprocess): sudo iptables-restore from (pid=4290) execute /root/openstack
2011-04-05 17:48:42,677 DEBUG nova.utils [-] Running cmd (subprocess): sudo iptables-save -t nat from (pid=4290) execute /root/openstack
2011-04-05 17:48:42,689 DEBUG nova.utils [-] Running cmd (subprocess): sudo iptables-restore from (pid=4290) execute /root/openstack
2011-04-05 17:48:42,718 DEBUG nova.utils [-] Running cmd (subprocess): mkdir -p /root/openstack
2011-04-05 17:48:42,726 INFO nova.virt.
2011-04-05 17:48:42,776 DEBUG nova.utils [-] Attempting to grab semaphore "115ec19b" for method "call_if_
2011-04-05 17:48:42,777 DEBUG nova.utils [-] Running cmd (subprocess): cp /root/openstack
2011-04-05 17:48:42,802 DEBUG nova.utils [-] Attempting to grab semaphore "0640184b" for method "call_if_
2011-04-05 17:48:42,811 ERROR nova.compute.
(nova.compute.
(nova.compute.
(nova.compute.
(nova.compute.
(nova.compute.
(nova.compute.
(nova.compute.
(nova.compute.
(nova.compute.
(nova.compute.
(nova.compute.
(nova.compute.
(nova.compute.
(nova.compute.
(nova.compute.
(nova.compute.
(nova.compute.
(nova.compute.
(nova.compute.
(nova.compute.
(nova.compute.
(nova.compute.
(nova.compute.
libvir: QEMU error : Domain not found: no domain with matching name 'instance-00000002'
2011-04-05 17:48:55,846 INFO nova.compute.
2011-04-05 17:48:55,847 INFO nova.compute.
Question information
- Language:
- English Edit question
- Status:
- Solved
- Assignee:
- No assignee Edit question
- Solved by:
- Hyunsun Moon
- Solved:
- 2011-04-06
- Last query:
- 2011-04-06
- Last reply:
- 2011-04-05
Vish Ishaya (vishvananda) said : | #1 |
You only need one scheduler. The error you are seeing is because need a way for the compute node on the second machine to retrieve images, either by sharing the folder that the local image service is using or by (recommended) installing glance and using
--image_
--glance_host=xxxx
Vish
On Apr 5, 2011, at 2:01 AM, Hyunsun Moon wrote:
> Question #151725 on OpenStack Compute (nova) changed:
> https:/
>
> Description changed to:
> Hello,
>
> I have deployed latest nova on 2 host machines, one for controller(nova-
> api, nova-scheduler, nova-network, nova-objectstore) and the other for
> compute(
>
> Problem is, as I hit run instance from the controller node, following compute error occurs on the compute node.
> nova-compute, nova-scheduler service was successfully added on the service table and euca-describe-
>
> root@cloud02:
> cloud02 nova-scheduler enabled :-) 2011-04-05 09:01:01
> cloud02 nova-network enabled :-) 2011-04-05 09:01:01
> cloud01 nova-scheduler enabled :-) 2011-04-05 08:59:23
> cloud01 nova-compute enabled :-) 2011-04-05 08:59:17
>
> root@cloud02:
> RESERVATION r-etss4atr NOVAADMPRJ default
> INSTANCE i-00000002 ami-0640184b 10.0.0.3 10.0.0.3 failed to spawn novaadm (NOVAADMPRJ, cloud01) 0 m1.small 2011-04-
>
>
> =======
>
> 2011-04-05 17:48:41,923 AUDIT nova.compute.
> 2011-04-05 17:48:42,018 DEBUG nova.rpc [-] Making asynchronous call on network.cloud02 ... from (pid=4290) call /root/openstack
> 2011-04-05 17:48:42,019 DEBUG nova.rpc [-] MSG_ID is 1d0b70e00fc94c1
> 2011-04-05 17:48:42,458 DEBUG nova.virt.
> 2011-04-05 17:48:42,531 DEBUG nova.virt.
> 2011-04-05 17:48:42,582 INFO nova [-] called setup_basic_
> 2011-04-05 17:48:42,582 INFO nova [-] ensuring static filters
> 2011-04-05 17:48:42,648 DEBUG nova.utils [-] Attempting to grab semaphore "iptables" for method "apply"... from (pid=4290) inner /root/openstack
> 2011-04-05 17:48:42,648 DEBUG nova.utils [-] Attempting to grab file lock "iptables" for method "apply"... from (pid=4290) inner /root/openstack
> 2011-04-05 17:48:42,653 DEBUG nova.utils [-] Running cmd (subprocess): sudo iptables-save -t filter from (pid=4290) execute /root/openstack
> 2011-04-05 17:48:42,665 DEBUG nova.utils [-] Running cmd (subprocess): sudo iptables-restore from (pid=4290) execute /root/openstack
> 2011-04-05 17:48:42,677 DEBUG nova.utils [-] Running cmd (subprocess): sudo iptables-save -t nat from (pid=4290) execute /root/openstack
> 2011-04-05 17:48:42,689 DEBUG nova.utils [-] Running cmd (subprocess): sudo iptables-restore from (pid=4290) execute /root/openstack
> 2011-04-05 17:48:42,718 DEBUG nova.utils [-] Running cmd (subprocess): mkdir -p /root/openstack
> 2011-04-05 17:48:42,726 INFO nova.virt.
> 2011-04-05 17:48:42,776 DEBUG nova.utils [-] Attempting to grab semaphore "115ec19b" for method "call_if_
> 2011-04-05 17:48:42,777 DEBUG nova.utils [-] Running cmd (subprocess): cp /root/openstack
> 2011-04-05 17:48:42,802 DEBUG nova.utils [-] Attempting to grab semaphore "0640184b" for method "call_if_
> 2011-04-05 17:48:42,811 ERROR nova.compute.
> (nova.compute.
> (nova.compute.
> (nova.compute.
> (nova.compute.
> (nova.compute.
> (nova.compute.
> (nova.compute.
> (nova.compute.
> (nova.compute.
> (nova.compute.
> (nova.compute.
> (nova.compute.
> (nova.compute.
> (nova.compute.
> (nova.compute.
> (nova.compute.
> (nova.compute.
> (nova.compute.
> (nova.compute.
> (nova.compute.
> (nova.compute.
> (nova.compute.
> (nova.compute.
> libvir: QEMU error : Domain not found: no domain with matching name 'instance-00000002'
> 2011-04-05 17:48:55,846 INFO nova.compute.
> 2011-04-05 17:48:55,847 INFO nova.compute.
>
> --
> You received this question notification because you are a member of Nova
> Core, which is an answer contact for OpenStack Compute (nova).
Everett Toews (everett-toews) said : | #2 |
You can find more info on using Glance with Nova at Configuring Image
Service and Storage for
Compute<http://
Running
Compute with the OpenStack Imaging
Service<http://
Hyunsun Moon (hyunsun-moon) said : | #3 |
Thanks Vish, Everett.
Solved this problem by mounting controller's images directory on the compute host using nfs.
Unfortunately, I have no Swift running on my system so that I cannot use Glance.
Vish Ishaya (vishvananda) said : | #4 |
FYI, you can use glance without swift. It has a local storage backend that will store the images on the filesystem of the glance host. Glad it is working though.
Vish
On Apr 6, 2011, at 12:19 AM, Hyunsun Moon wrote:
> Question #151725 on OpenStack Compute (nova) changed:
> https:/
>
> Status: Answered => Solved
>
> Hyunsun Moon confirmed that the question is solved:
> Thanks Vish, Everett.
> Solved this problem by mounting controller's images directory on the compute host using nfs.
> Unfortunately, I have no Swift running on my system so that I cannot use Glance.
>
> --
> You received this question notification because you are a member of Nova
> Core, which is an answer contact for OpenStack Compute (nova).
Hyunsun Moon (hyunsun-moon) said : | #5 |
Great! I will try Glance, too.