Look at comment #2, it’s me. > On Nov 2, 2017, at 11:34 AM, Sergio Cuellar Valdes > <scuell...@kionetworks.com> wrote: > > Hi Mike, > > Which version of OpenStack are you using ? Do the normal migrations work ? > > I found a bug that looks like your problem [1] > > [1] https://bugs.launchpad.net/nova/+bug/1715569 > <https://bugs.launchpad.net/nova/+bug/1715569> > > Cheers, > Sergio > > On 2 November 2017 at 08:48, Mike Lowe <joml...@iu.edu > <mailto:joml...@iu.edu>> wrote: > After moving from CentOS 7.3 to 7.4, I’ve had trouble getting live migration > to work when a volume is attached. As it turns out when a live migration > takes place the libvirt driver rewrites portions of the xml definition for > the destination hypervisor and gets it wrong. Here is an example. > > It turns this: > > disk device="disk" type="network"> > <driver cache="writeback" name="qemu" type="raw"/> > <auth username="cinder"> > <secret type="ceph" > uuid="1a790a26-dd49-4825-8d16-3dd627cf05a9"/> > </auth> > <source > name="cinder-volumes/volume-de400476-b68a-45a2-b04f-739313f42bef" > protocol="rbd"> > <host name="172.16.128.101" port="6789"/> > <host name="172.16.128.121" port="6789"/> > <host name="172.16.128.130" port="6789"/> > </source> > <target bus="scsi" dev="sdb"/> > <serial>de400476-b68a-45a2-b04f-739313f42bef</serial> > <address bus="0" controller="0" target="0" type="drive" unit="1"/> > </disk> > > Into this: > > <disk device="disk" type="network"> > <driver cache="writeback" name="qemu" type="raw"/> > <auth username="cinder"> > <secret type="ceph" > uuid="1a790a26-dd49-4825-8d16-3dd627cf05a9"/> > </auth> > <source > name="cinder-volumes/volume-de400476-b68a-45a2-b04f-739313f42bef" > protocol="rbd"> > <host name="172.16.128.101" port="6789"/> > <host name="172.16.128.121" port="6789"/> > <host name="172.16.128.130" port="6789"/> > </source> > <target bus="scsi" dev="sdb"/> > <serial>de400476-b68a-45a2-b04f-739313f42bef</serial> > <address controller="0" type="drive"/> > </disk> > > Note the address change, libvirt will attempt to put this undefined disk at > 0:0:0 which conflicts with the root disk and causes the migration to fail. > While this may be a libvirt bug I can’t imagine anything good would come from > changing the scsi address of your disks mid flight so steps should be taken > in nova if rewriting the definition to preserve the address. > > Here is my question, when exactly would you want to change the definition of > an attached volume? > > > > _______________________________________________ > OpenStack-operators mailing list > OpenStack-operators@lists.openstack.org > <mailto:OpenStack-operators@lists.openstack.org> > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators > <http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators> > > > > -- > Sergio Cuéllar │DevOps Engineer > KIO NETWORKS > Mexico City Phone (52) 55 8503 2600 ext. 4335 > Mobile: 5544844298 > www.kionetworks.com <http://www.kionetworks.com/> > > > *********************************************************************************************************************** > “Este mensaje es confidencial. Si usted no es el destinatario de este > mensaje, le suplicamos se lo notifique al remitente mediante un correo > electrónico y que borre el presente mensaje y sus anexos de su computadora > sin retener una copia de los mismos. No debe copiar este mensaje o usarlo > para cualquier propósito ni divulgar su contenido. KIO Networks se reserva el > derecho de monitorear todas las comunicaciones de correo electrónico > (relacionadas o no con KIO Networks) que se transmitan a través de su > sistema. Muchas gracias. > This email is confidential and may also be privileged. If you are not the > intended recipient please immediately advise the sender by reply e-mail and > delete this message and its attachments from your computer without retaining > a copy. You should not copy it or use it for any purpose nor disclose its > contents to any other person. KIO Networks reserves the right to monitor all > email communications (whether related to the business of KIO Networks or not) > through its networks. Thank you.” > > ***********************************************************************************************************************_______________________________________________ > OpenStack-operators mailing list > OpenStack-operators@lists.openstack.org > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
_______________________________________________ OpenStack-operators mailing list OpenStack-operators@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
