This bug was fixed in the package libvirt - 1.3.1-1ubuntu10.29
---
libvirt (1.3.1-1ubuntu10.29) xenial; urgency=medium
* debian/patches/lp1681839-*.patch: Fix block commit timeout
races, and ensure that once commit has reached 100%, timeouts
no longer apply. (LP: #1681839)
The customer has been unresponsive in testing the package in -proposed
in their environment, so we will move on with verification.
In my previous comment on 2019-11-27, we showed that libvirt
1.3.1-1ubuntu10.29 can successfully execute a blockcommit on a lvm
backed volume with virsh.
This still
The following is verification performed by Fabio in a lab:
- Tested with the original libvirt to make sure I was able to reproduce:
root@ubuntu:~# apt-cache policy libvirt-bin
libvirt-bin:
Installed: 1.3.1-1ubuntu10.27
Candidate: 1.3.1-1ubuntu10.27
Version table:
*** 1.3.1-1ubuntu10.27 500
500
@mruffel / @fabiomartins - would you be so kind doing the SRU
verification on this one?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1681839
Title:
libvirt: blockcommit fails - disk not ready for
I thank you for all your work.
I have since moved away from this block architecture and am no longer able
to verify with an existing configuration.
On Fri, Nov 22, 2019 at 6:36 AM Timo Aaltonen
wrote:
> Hello Patrick, or anyone else affected,
>
> Accepted libvirt into xenial-proposed. The
Hello Patrick, or anyone else affected,
Accepted libvirt into xenial-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/libvirt/1.3.1-1ubuntu10.29 in a few
hours, and then in the -proposed repository.
Please help us by testing this new package. See
FYI: my pre-checks on the PPA build 1.3.1-1ubuntu10.29~ppa1 look good.
prep (x86_64): Pass 25 F/S/N 0/0/0 - RC 0 (17 min 84141 lin)
migrate (x86_64) : Pass 232 F/S/N 0/12/0 - RC 0 (63 min 104302 lin)
cross (x86_64) : Pass 64 F/S/N 0/1/0 - RC 0 (70 min 94458 lin)
misc (x86_64):
Hi Mathew,
thanks for picking up the torch again on this issue that affected quite some
people, but but so far never reached the state to be really fixable.
## Verification ##
Most importantly was to get some repro for test and verification.
This was formerly a big issue, it affected plenty of
Thanks++
Now that I had (new) steps to recreate I could work on those.
I wondered if an LVM is really strictly needed - which would also easen the
initialization.
So I simplified it to.
$ apt install uvtool-libvirt
$ uvt-simplestreams-libvirt sync --source http://cloud-images.ubuntu.com/daily
Tagged and sponsored to Xenial-unapproved.
Now it is up to the SRU Team.
@Matthew - please try to get as much testing in place as possible.
As I said all but the final verification can be done either on the PPA in
advance or once in -proposed. As it fits your time and setup.
I'll setup a test
For the sake of seeing it trigger at least once I redeployed a mchine with
Xenial to create LVMs there on a free /dev/sdb disk as your example needs it.
# create guest
$ uvt-simplestreams-libvirt --verbose sync --source
http://cloud-images.ubuntu.com/daily arch=amd64 label=daily release=xenial
$
Attached is the debdiff for xenial to fix this issue.
I was not sure if the patches in debian/patches should be placed in the
debian/patches/ubuntu directory or not, so I left them outside. Feel
free to move them if necessary.
** Patch added: "libvirt debdiff for xenial"
** Summary changed:
- libvirt - disk not ready for pivot yet
+ libvirt: blockcommit fails - disk not ready for pivot yet
** Description changed:
- root@thewind:/home/bestpa/scripts# virsh blockcommit mail vda --active
--verbose --pivot
- Block commit: [100 %]error: failed to pivot job for disk
13 matches
Mail list logo
