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,
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
The patches: c285ffc4, 7eabd55, 676cb4f4 are all in 1.2.8 and that
version is in Utopic so marking Fix Released for that version.
** Changed in: libvirt (Ubuntu)
Status: In Progress = Fix Released
** Changed in: libvirt (Ubuntu Trusty)
Status: New = Fix Committed
** Tags added:
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.
** Also affects: libvirt (Ubuntu Precise)
Importance:
