[Pkg-libvirt-maintainers] Bug#867379: restarting libvirtd can still loose containers

Christian Ehrhardt christian.ehrhardt at canonical.com
Thu Jul 6 06:51:44 UTC 2017


Package: libvirt
Version: 3.0.0-4
Severity: normal

Hi,
opening a new bug which is related to the former 848317
The old bug was about issues in the autopkgtests which are fixed since 3.0
due to upstream changes on cgroup placement.
Yet I happened to find that they still affect me in Ubuntu on the test, but
not on Debian.

It turned out, that the difference why this is blocking my tests but not
Debian is almost an accident - there are good and bad states and Debian
seems in the good one on the tests.
But I can recreate the issue on both distributions with the 3.0 as in
Debian but also with experiments on up to 3.5 in Ubuntu.

Script to reproduce and log some related data:
  http://paste.ubuntu.com/25030388/

I've made some progress, but want to start documenting and discussing that
with you so you are aware and can let me know if you have any further ideas
around resolving that.

P.S. severity normal since while it seems rare potentially loosing state
that was in containers, please feel free to adapt if you think otherwise.
Also it is not understood enough if there are other ways to get into bad
state, so more might be affected.

-- 
Christian Ehrhardt
Software Engineer, Ubuntu Server
Canonical Ltd
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.alioth.debian.org/pipermail/pkg-libvirt-maintainers/attachments/20170706/36735695/attachment.html>


More information about the Pkg-libvirt-maintainers mailing list