Reviewed: https://review.openstack.org/591080 Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=f046d8b54009978a3c83939dc190edbc1ebc09ae Submitter: Zuul Branch: master
commit f046d8b54009978a3c83939dc190edbc1ebc09ae Author: melanie witt <melwi...@gmail.com> Date: Fri Aug 10 20:28:41 2018 +0000 Handle unicode characters in migration params There can be unicode characters in the params for live migration, for example, the guest domain name in the destination XML. We need to convert those to bytes when we call migrateToURI3 under python2. The existing code was just calling str() for this, but that will fail with the error: UnicodeEncodeError: 'ascii' codec can't encode characters... We need to encode the unicode characters to do conversion. The existing unit test wasn't using any unicode characters in its test data, so this scenario wasn't covered. Closes-Bug: #1768807 Change-Id: I4b34139a3c5e3e2b7cf7cbe50bdf3da3131b9b1c ** Changed in: nova Status: In Progress => Fix Released -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Compute (nova). https://bugs.launchpad.net/bugs/1768807 Title: Live Migration failure: 'ascii' codec can't encode characters in position 251-252 Status in OpenStack Compute (nova): Fix Released Bug description: when i do live migration,it raise the error as below: 2018-05-03 18:38:00.838 1570085 ERROR nova.virt.libvirt.driver [req- 7a3691d2-f850-4258-8c7a-54dcaa6189aa 659e4083e38046f8a23060addb53bd96 58942649d31846858f033ee805fcb5bc - default default] [instance: b9f91fe7-70b0-4efc-800a-0482914da186] Live Migration failure: 'ascii' codec can't encode characters in position 251-252: ordinal not in range(128): UnicodeEncodeError: 'ascii' codec can't encode characters in position 251-252: ordinal not in range(128) I have two computer node: compute1 ,compute2. The instance created at compute2 migrate to compute1 and migrate back to compute2 is work well. But the instance created at compute1 migrate to compute2 will make a fault as above. The two node configure file is same as well. To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1768807/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp