On Thu, Sep 7, 2017 at 11:32 AM, Milan Zamazal <mzamazal(a)redhat.com> wrote:
Piotr Kliczewski <piotr.kliczewski(a)gmail.com> writes:
> There few ways I could get there:
> 1. Testing some code and creating vdsm and later dropping db and
> reinstalling the host with "new db"
> 2. Vms provisioned manually.
I.e. outside oVirt? If they are external VMs then it explains why you
get the tracebacks and we have a fix posted
(
https://gerrit.ovirt.org/81529). I was worried that the tracebacks
could be caused by oVirt VMs.
Not in this case.
> At this time it seems to be option #2 and I see:
>
> [root@f20 ~]# virsh -r list --all
> Id Name State
> ----------------------------------------------------
> - centos7 shut off
> - rhel7.0-dev shut off
>
> which are machines where I test el7 compatibility of my changes (I use
> fedora25 on bare metal).
>
> I see the failure every time I run the engine now since I sent the
> email to this thread. It started
> to occur recently event though I have those vms there for really long time.