'virsh migrate' fails in a password authentication of SSH

Thanks for submitting this bug and posting patches! Do the patches
definately fix it for you? (I had always thought the cause was
different, so was surprised to see the patches are handling network
timeout)

Setting the priority to medium since there is a workaround (using
ssh keys)

 importance: medium

Hello

There was a poll function problem waiting STDIN on PTS env ( on ssh ). so looks hang.

I emailed patch (not this) to the maintainer of libvirt, but they told me about this commits ( attached ).

then I applied this patch and tested on my machines. and It worked.

and the customer (NEC) also tested this.

Thanks.

Thanks. so those should be fixed in the 1.2.8 version we are trying to upload (awaiting FFE) to utopic now. Note also that commit 7eabd55. introduced a regression fixed by c285ffc4.

We can SRU these into trusty once they are in utopic.

Thanks.

got c285ffc4, applied patch is uploaded.

thank you. I've gone with keeping the three patches separate, so that in 3-4 years it's easier to tell what has and has not been applied based on the git tree, however having your patch to sanity-check and make sure we got the same result was still very useful.

The patches: c285ffc4, 7eabd55, 676cb4f4 are all in 1.2.8 and that version is in Utopic so marking Fix Released for that version.

Hello Seyeong, or anyone else affected,

Accepted libvirt into trusty-proposed. The package will build now and be available at http://launchpad.net/ubuntu/+source/libvirt/1.2.2-0ubuntu13.1.6 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance!

I confirmed the packages work well on my test machines

Thanks

The verification of the Stable Release Update for libvirt has completed successfully and the package has now been released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions.

This bug was fixed in the package libvirt - 1.2.2-0ubuntu13.1.6

---------------
libvirt (1.2.2-0ubuntu13.1.6) trusty-proposed; urgency=medium

  * 9029-ovs-delete-port-if-it-exists-when-adding-new-one: cherrypick commit
    33445ce from upstream (LP: #1343262)
  * fix migration failure with ssh password authentication (LP: #1365947)
    - 9030-virsh-add-keepalive-in-new-vshconnect-fn
    - 9031-cmdmigrate-move-vshconnect-before-vshwatchjob
    - 9032-virsh-initialize-vsh-data-in-cmdmigrate
  * libvirt-bin.postinst: check for confiles whichhave been removed rather
    than fail package install (LP: #1375910)
  * Support incoming migration from 12.04 hosts (LP: #1374622)
    - debian/patches/support-incoming-qemu-kvm: add a flag to
      /etc/libvirt/qemu.conf to specify whether pc-1.0 came from a 12.04 host
    - Add a note in README.Debian.
 -- Serge Hallyn <email address hidden> Tue, 30 Sep 2014 13:54:31 -0500

This code has changed quite a bit since precise, and I don't want to accidentally cause a regression. Given that there is a workaround (using ssh keys) I am going to drop the priority of this and mark it wont-fix. If someone can describe a case where using ssh keys cannot work as a workaround, we can consider re-raising the priority.