Bug 1840414

Yet another block merge. Milan, Nir, dupe?

The Vdsm traceback and error message look the same as in bug 1785939. Marco, does it happen with libvirt >= 6.0.0-17.module+el8.2.0+6257+0d066c28?

Milan, would like to test it -- is there a ovirt-node pre-release I can use?
Or do I need to start from Centos 8.2?

Not sure on how best to get libvirt 6 on the current setup (ovirt-node 4.4.0)

Thanks,
Marco

I don't know about ovirt-node releases, some pre-releases are listed at https://www.ovirt.org/download/node.html, I guess "Latest master" could already include libvirt 6. CentOS Advanced Virt was updated with libvirt 6 etc. last week, it should be available with current ovirt-release-master package, but beware, there may be other issues with the updated versions.

If you manage to test it with libvirt 6, please update this bug. Once libvirt 6 in CentOS Advanced Virt stabilizes, we should require it also for CentOS in Vdsm dependencies.

could you please check with centos stream?

Hi Arik,

I have just checked CentOS Stream and I see it ships with libvirt 4.5.0:

libvirt-4.5.0-35.3.module_el8.1.0+297+df420408.x86_64

So I don't think it would be a useful test...
Can't find the advanced virtualization packages for CentOS Stream -- any suggestion?

In the meantime I can confirm the bug is there in three different environment (all based on oVirt-node 4.4.0) and is always 100% reproducible.

Regards,
Marco

(In reply to Marco Fais from comment #6)
>
> I have just checked CentOS Stream and I see it ships with libvirt 4.5.0:
> 
> libvirt-4.5.0-35.3.module_el8.1.0+297+df420408.x86_64
> 
> So I don't think it would be a useful test...
> Can't find the advanced virtualization packages for CentOS Stream -- any
> suggestion?

Hi Marco, if you are willing to check the latest oVirt Node Master from https://www.ovirt.org/download/node.html, it contains the new libvirt. The current ovirt-release-master package also sets up the following repo, which contains up to date versions of libvirt and QEMU:

  [ovirt-master-advanced-virtualization-testing]
  name=Advanced Virtualization testing packages for $basearch
  baseurl=https://buildlogs.centos.org/centos/8/virt/$basearch/advanced-virtualization/
  enabled=1
  gpgcheck=0
  module_hotfixes=1

You can try either oVirt Node Master or the ovirt-release-master package or adding the repo manually. It's all master, so you risk replacing old bugs with new ones, but you may want to try it on one of your hosts whether it fixes your snapshot problem. Please let us know.

> Hi Marco, if you are willing to check the latest oVirt Node Master from
> https://www.ovirt.org/download/node.html, it contains the new libvirt. The
> current ovirt-release-master package also sets up the following repo, which
> contains up to date versions of libvirt and QEMU:
> 
>   [ovirt-master-advanced-virtualization-testing]
>   name=Advanced Virtualization testing packages for $basearch
>  
> baseurl=https://buildlogs.centos.org/centos/8/virt/$basearch/advanced-
> virtualization/
>   enabled=1
>   gpgcheck=0
>   module_hotfixes=1
> 
> You can try either oVirt Node Master or the ovirt-release-master package or
> adding the repo manually. It's all master, so you risk replacing old bugs
> with new ones, but you may want to try it on one of your hosts whether it
> fixes your snapshot problem. Please let us know.

Hi Milan,

thanks a million -- that's exactly what I needed!

I have added the repository in one of my ovirt-node-4.4.0 hosts and installed the packages (I had to disable the versionlock plugin in order to upgrade the existing versions).
I can confirm everything works fine with the packages in the testing repository:

libvirt-daemon.x86_64                             6.0.0-17.el8
libguestfs.x86_64                                 1.40.2-22.el8
qemu-kvm.x86_64                                   4.2.0-19.el8
(and the other relevant packages)

Storage backend used is glusterfs replica 3 -- I have problems (qemu crashes) removing snapshots with a distributed-disperse backend but looking at the logs it might be a problem with the gluster storage rather than qemu-kvm.

If you need any logs let me know. If I use the same VM/same backend on a standard ovirt-node-4.4.0 system I can replicate the issues again.

Should I roll-out the repository to the rest of the cluster or should I wait for the above to be integrated in a future ovirt-node release?

Thanks again for your help...
Marco

(In reply to Marco Fais from comment #8)
> Storage backend used is glusterfs replica 3 -- I have problems (qemu
> crashes) removing snapshots with a distributed-disperse backend but looking
> at the logs it might be a problem with the gluster storage rather than
> qemu-kvm.
> 
> If you need any logs let me know. If I use the same VM/same backend on a
> standard ovirt-node-4.4.0 system I can replicate the issues again.

Sounds like a different issue, if you'd like us to take a look into that please file a separate bug.

> 
> Should I roll-out the repository to the rest of the cluster or should I wait
> for the above to be integrated in a future ovirt-node release?

As Milan wrote above, by using that repo "you risk replacing old bugs with new ones".
It really depends on the risk you're willing to take for using, possibly, less mature tools but that address the reported issue.

(In reply to Arik from comment #9)

Arik, 

thanks for your comments

> > If you need any logs let me know. If I use the same VM/same backend on a
> > standard ovirt-node-4.4.0 system I can replicate the issues again.
> 
> Sounds like a different issue, if you'd like us to take a look into that
> please file a separate bug.

I have opened an issue with the gluster team -- see here: https://github.com/gluster/glusterfs/issues/1309
Not sure if/where to track it on the oVirt side...

> > Should I roll-out the repository to the rest of the cluster or should I wait
> > for the above to be integrated in a future ovirt-node release?
> 
> As Milan wrote above, by using that repo "you risk replacing old bugs with
> new ones".
> It really depends on the risk you're willing to take for using, possibly,
> less mature tools but that address the reported issue.

Thanks -- I will roll-out only on our test cluster for the moment until I get more clarify on which ovirt-node release will contain the updated qemu/libvirt packages.

Regards,
Marco

The only thing that I see to do here is adding a newer libvirt version as a dependency of VDSM, once available on centos.

This bugzilla is included in oVirt 4.4.2 release, published on September 17th 2020.

Since the problem described in this bug report should be resolved in oVirt 4.4.2 release, it has been closed with a resolution of CURRENT RELEASE.

If the solution does not work for you, please open a new bug report.