[Openstack-operators] live migration problem

Sergio Ariel de la Campa Saiz sacampa at gmv.com
Tue May 22 14:47:38 UTC 2012


Hi:

First of all thanks!!!


This is my enviroment:

opst1=controller (compute, network, glance, keystone)
opst3=node (compute, network)
CASE1: instances created in opst1 (controller) migrate OK from one to another (each way)
CASE2: instances created in opst3 (node) can´t be migrated to opst1 (controller), nothing happens, instances keep in opst3



These are my logs:


CASE1 (instance created in controller migrates to node, opst1->opst3):

nova-compute.log from opst3 (node)

2012-05-22 16:26:10 INFO nova.compute.manager [-] post_live_migration() is started..
2012-05-22 16:26:11 INFO nova.compute.manager [-] [instance: c8ba24d3-a36c-46a0-8d3e-c27a26a7c970] No floating_ip found
2012-05-22 16:26:15 WARNING nova.compute.manager [-] Found 2 in the database and 1 on the hypervisor.
2012-05-22 16:26:16 INFO nova.compute.manager [-] During the sync_power process the instance c8ba24d3-a36c-46a0-8d3e-c27a26a7c970 has moved from host opst3 to host opst1
2012-05-22 16:26:16 ERROR nova.manager [-] Error during ComputeManager._sync_power_states: local variable 'vm_power_state' referenced before assignment
2012-05-22 16:26:16 TRACE nova.manager Traceback (most recent call last):
2012-05-22 16:26:16 TRACE nova.manager   File "/usr/lib/python2.7/dist-packages/nova/manager.py", line 155, in periodic_tasks
2012-05-22 16:26:16 TRACE nova.manager     task(self, context)
2012-05-22 16:26:16 TRACE nova.manager   File "/usr/lib/python2.7/dist-packages/nova/compute/manager.py", line 2359, in _sync_power_states
2012-05-22 16:26:16 TRACE nova.manager     if vm_power_state == db_power_state:
2012-05-22 16:26:16 TRACE nova.manager UnboundLocalError: local variable 'vm_power_state' referenced before assignment
2012-05-22 16:26:16 TRACE nova.manager
2012-05-22 16:26:24 INFO nova.virt.libvirt.connection [-] Compute_service record updated for opst3
2012-05-22 16:26:24 INFO nova.compute.manager [-] [instance: c8ba24d3-a36c-46a0-8d3e-c27a26a7c970] Migrating instance to opst1 finished successfully.
2012-05-22 16:26:24 INFO nova.compute.manager [-] [instance: c8ba24d3-a36c-46a0-8d3e-c27a26a7c970] You may see the error "libvirt: QEMU error: Domain not found: no domain with matching name." This error can be safely ignored.


nova-compute.log from opst1 (controller)

2012-05-22 16:26:43 INFO nova.virt.libvirt.connection [req-c891d605-35a2-4d43-9263-6c1de9c31f22 11e65be4a735407b876949b6018fb7ab b0240032bb0241939b55037ec98a9988] Instance launched has CPU info:
{"vendor": "Intel", "model": "Penryn", "arch": "x86_64", "features": ["dca", "xtpr", "tm2", "est", "vmx", "ds_cpl", "monitor", "pbe", "tm", "ht", "ss", "acpi", "ds", "vme"], "topology": {"cores": "4", "threads": "1", "sockets": "2"}}
2012-05-22 16:26:43 INFO nova.virt.libvirt.connection [req-c891d605-35a2-4d43-9263-6c1de9c31f22 11e65be4a735407b876949b6018fb7ab b0240032bb0241939b55037ec98a9988] to xml...
:<cpu>
    <arch>x86_64</arch>
    <model>Penryn</model>
    <vendor>Intel</vendor>
    <topology sockets="2" cores="4" threads="1"/>
    <features name="dca" />
    <features name="xtpr" />
    <features name="tm2" />
    <features name="est" />
    <features name="vmx" />
    <features name="ds_cpl" />
    <features name="monitor" />
    <features name="pbe" />
    <features name="tm" />
    <features name="ht" />
    <features name="ss" />
    <features name="acpi" />
    <features name="ds" />
    <features name="vme" />
</cpu>
2012-05-22 16:26:45 INFO nova.compute.manager [req-c891d605-35a2-4d43-9263-6c1de9c31f22 11e65be4a735407b876949b6018fb7ab b0240032bb0241939b55037ec98a9988] [instance: c8ba24d3-a36c-46a0-8d3e-c27a26a7c970] Instance has no volume.
2012-05-22 16:26:45 INFO nova.virt.libvirt.firewall [req-c891d605-35a2-4d43-9263-6c1de9c31f22 11e65be4a735407b876949b6018fb7ab b0240032bb0241939b55037ec98a9988] [instance: c8ba24d3-a36c-46a0-8d3e-c27a26a7c970] Called setup_basic_filtering in nwfilter
2012-05-22 16:26:45 INFO nova.virt.libvirt.firewall [req-c891d605-35a2-4d43-9263-6c1de9c31f22 11e65be4a735407b876949b6018fb7ab b0240032bb0241939b55037ec98a9988] [instance: c8ba24d3-a36c-46a0-8d3e-c27a26a7c970] Ensuring static filters
2012-05-22 16:26:58 INFO nova.compute.manager [req-c891d605-35a2-4d43-9263-6c1de9c31f22 11e65be4a735407b876949b6018fb7ab b0240032bb0241939b55037ec98a9988] [instance: c8ba24d3-a36c-46a0-8d3e-c27a26a7c970] Post operation of migraton started
2012-05-22 16:27:23 INFO nova.virt.libvirt.connection [-] Compute_service record updated for opst1
2012-05-22 16:27:23 INFO nova.compute.manager [-] Updating host status



CASE2 (instance created in node try to migrate to controller, opst3->opst1):

nova-compute.log from controller (opst1):

2012-05-22 16:18:14 INFO nova.virt.libvirt.connection [req-b70b9efa-7dec-4aac-a27e-415e1ea26ba2 11e65be4a735407b876949b6018fb7ab b0240032bb0241939b55037ec98a9988] Instance launched has CPU info:
{"vendor": "Intel", "model": "Penryn", "arch": "x86_64", "features": ["dca", "xtpr", "tm2", "est", "vmx", "ds_cpl", "monitor", "pbe", "tm", "ht", "ss", "acpi", "ds", "vme"], "topology": {"cores": "4", "threads": "1", "sockets": "2"}}
2012-05-22 16:18:14 INFO nova.virt.libvirt.connection [req-b70b9efa-7dec-4aac-a27e-415e1ea26ba2 11e65be4a735407b876949b6018fb7ab b0240032bb0241939b55037ec98a9988] to xml...
:<cpu>
    <arch>x86_64</arch>
    <model>Penryn</model>
    <vendor>Intel</vendor>
    <topology sockets="2" cores="4" threads="1"/>
    <features name="dca" />
    <features name="xtpr" />
    <features name="tm2" />
    <features name="est" />
    <features name="vmx" />
    <features name="ds_cpl" />
    <features name="monitor" />
    <features name="pbe" />
    <features name="tm" />
    <features name="ht" />
    <features name="ss" />
    <features name="acpi" />
    <features name="ds" />
    <features name="vme" />
</cpu>
2012-05-22 16:18:15 INFO nova.compute.manager [req-b70b9efa-7dec-4aac-a27e-415e1ea26ba2 11e65be4a735407b876949b6018fb7ab b0240032bb0241939b55037ec98a9988] [instance: e1b11fce-56f7-4c30-bb68-adb0910a2b02] Instance has no volume.
2012-05-22 16:18:16 INFO nova.virt.libvirt.firewall [req-b70b9efa-7dec-4aac-a27e-415e1ea26ba2 11e65be4a735407b876949b6018fb7ab b0240032bb0241939b55037ec98a9988] [instance: e1b11fce-56f7-4c30-bb68-adb0910a2b02] Called setup_basic_filtering in nwfilter
2012-05-22 16:18:16 INFO nova.virt.libvirt.firewall [req-b70b9efa-7dec-4aac-a27e-415e1ea26ba2 11e65be4a735407b876949b6018fb7ab b0240032bb0241939b55037ec98a9988] [instance: e1b11fce-56f7-4c30-bb68-adb0910a2b02] Ensuring static filters
2012-05-22 16:18:22 INFO nova.virt.libvirt.connection [-] Compute_service record updated for opst1
2012-05-22 16:18:23 INFO nova.compute.manager [-] Updating host status


nova-compute.log from node (opst3):

2012-05-22 16:17:50 INFO nova.virt.libvirt.connection [-] Compute_service record updated for opst3
2012-05-22 16:17:50 INFO nova.compute.manager [-] Updating host status



Regards....

Sergio Ariel
de la Campa Saiz
GMV-SES Infraestructura /
GMV-SES Infrastructure





GMV
Isaac Newton, 11
P.T.M. Tres Cantos
E-28760 Madrid
Tel.
+34 91 807 21 00
Fax
+34 91 807 21 99
 www.gmv.com








________________________________
De: Paride Letizia [letizia_paride at yahoo.it]
Enviado el: martes, 22 de mayo de 2012 16:04
Para: Sergio Ariel de la Campa Saiz
Asunto: Re: [Openstack-operators] live migration problem

Hi can you post the Compute log when you run an instance on the controller and then migrate it into opst1?
________________________________
Da: Sergio Ariel de la Campa Saiz <sacampa at gmv.com>
A: "openstack at lists.launchpad.net" <openstack at lists.launchpad.net>; "openstack-operators at lists.openstack.org" <openstack-operators at lists.openstack.org>; "openstack-operators-bounces at lists.openstack.org" <openstack-operators-bounces at lists.openstack.org>
Inviato: Martedì 22 Maggio 2012 13:19
Oggetto: [Openstack-operators] live migration problem

Hi:

I appreciate you help me :-)

I´m facing with a problem about live migration. I have 2 nodes (opst1 is the controller, and opst3 is a compute and a network node)
When I create an instance in the controller and migrate it to the other node there is no problem, all works correctly.
But when I create an instance in the other node and I try to migrate it to the controller, nothing happens (no migration occurs). I can´t find any error in logs. In fact, next I show you my nova-compute logs of controller. This is when I try to migrate the instance from opst3 to the controller (opst1).

2012-05-22 13:07:16 INFO nova.virt.libvirt.connection [req-f1f597ab-1c1d-421c-a606-7806740c6856 d7902da43c604c49baee92f8fdd8595f b0240032bb0241939b55037ec98a9988] Instance launched has CPU info:
{"vendor": "Intel", "model": "Penryn", "arch": "x86_64", "features": ["dca", "xtpr", "tm2", "est", "vmx", "ds_cpl", "monitor", "pbe", "tm", "ht", "ss", "acpi", "ds", "vme"], "topology": {"cores": "4", "threads": "1", "sockets": "2"}}
2012-05-22 13:07:16 INFO nova.virt.libvirt.connection [req-f1f597ab-1c1d-421c-a606-7806740c6856 d7902da43c604c49baee92f8fdd8595f b0240032bb0241939b55037ec98a9988] to xml...
:<cpu>
    <arch>x86_64</arch>
    <model>Penryn</model>
    <vendor>Intel</vendor>
    <topology sockets="2" cores="4" threads="1"/>
    <features name="dca" />
    <features name="xtpr" />
    <features name="tm2" />
    <features name="est" />
    <features name="vmx" />
    <features name="ds_cpl" />
    <features name="monitor" />
    <features name="pbe" />
    <features name="tm" />
    <features name="ht" />
    <features name="ss" />
    <features name="acpi" />
    <features name="ds" />
    <features name="vme" />
</cpu>
2012-05-22 13:07:17 INFO nova.compute.manager [req-f1f597ab-1c1d-421c-a606-7806740c6856 d7902da43c604c49baee92f8fdd8595f b0240032bb0241939b55037ec98a9988] [instance: a0bb85d7-5250-499c-883b-570ebd364446] Instance has no volume.
2012-05-22 13:07:18 INFO nova.virt.libvirt.firewall [req-f1f597ab-1c1d-421c-a606-7806740c6856 d7902da43c604c49baee92f8fdd8595f b0240032bb0241939b55037ec98a9988] [instance: a0bb85d7-5250-499c-883b-570ebd364446] Called setup_basic_filtering in nwfilter
2012-05-22 13:07:18 INFO nova.virt.libvirt.firewall [req-f1f597ab-1c1d-421c-a606-7806740c6856 d7902da43c604c49baee92f8fdd8595f b0240032bb0241939b55037ec98a9988] [instance: a0bb85d7-5250-499c-883b-570ebd364446] Ensuring static filters
2012-05-22 13:08:15 INFO nova.virt.libvirt.connection [-] Compute_service record updated for opst1
2012-05-22 13:09:23 INFO nova.virt.libvirt.connection [-] Compute_service record updated for opst1
2012-05-22 13:09:23 INFO nova.compute.manager [-] Updating host status

Thanks a lot!!!!


Sergio Ariel

de la Campa Saiz

GMV-SES Infraestructura /
GMV-SES Infrastructure









GMV

Isaac Newton, 11
P.T.M. Tres Cantos
E-28760 Madrid
Tel.

+34 91 807 21 00
Fax

+34 91 807 21 99
www.gmv.com









________________________________
This message including any attachments may contain confidential information, according to our Information Security Management System, and intended solely for a specific individual to whom they are addressed. Any unauthorised copy, disclosure or distribution of this message is strictly forbidden. If you have received this transmission in error, please notify the sender immediately and delete it.
________________________________
Este mensaje, y en su caso, cualquier fichero anexo al mismo, puede contener información clasificada por su emisor como confidencial en el marco de su Sistema de Gestión de Seguridad de la Información siendo para uso exclusivo del destinatario, quedando prohibida su divulgación copia o distribución a terceros sin la autorización expresa del remitente. Si Vd. ha recibido este mensaje erróneamente, se ruega lo notifique al remitente y proceda a su borrado. Gracias por su colaboración.
________________________________
Esta mensagem, incluindo qualquer ficheiro anexo, pode conter informação confidencial, de acordo com nosso Sistema de Gestão de Segurança da Informação, sendo para uso exclusivo do destinatário e estando proibida a sua divulgação, cópia ou distribuição a terceiros sem autorização expressa do remetente da mesma. Se recebeu esta mensagem por engano, por favor avise de imediato o remetente e apague-a. Obrigado pela sua colaboração.
________________________________

_______________________________________________
Openstack-operators mailing list
Openstack-operators at lists.openstack.org<mailto:Openstack-operators at lists.openstack.org>
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators



______________________
This message including any attachments may contain confidential 
information, according to our Information Security Management System,
 and intended solely for a specific individual to whom they are addressed.
 Any unauthorised copy, disclosure or distribution of this message
 is strictly forbidden. If you have received this transmission in error,
 please notify the sender immediately and delete it.

______________________
Este mensaje, y en su caso, cualquier fichero anexo al mismo,
 puede contener informacion clasificada por su emisor como confidencial
 en el marco de su Sistema de Gestion de Seguridad de la 
Informacion siendo para uso exclusivo del destinatario, quedando 
prohibida su divulgacion copia o distribucion a terceros sin la 
autorizacion expresa del remitente. Si Vd. ha recibido este mensaje 
 erroneamente, se ruega lo notifique al remitente y proceda a su borrado. 
Gracias por su colaboracion.

______________________

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-operators/attachments/20120522/c6ed146a/attachment-0002.html>


More information about the Openstack-operators mailing list