[ovirt-devel] Re: Changing vdsm version installed on host

Nir Soffer <nsoffer(a)redhat.com&gt; writes: > On Mon, Apr 20, 2020 at 11:34 PM Vojtech Juranek <vjuranek(a)redhat.com&gt; > wrote: >> >> >> On pondělí 20. dubna 2020 22:20:22 CEST Nir Soffer wrote: > > > >> > On Mon, Apr 20, 2020 at 11:16 PM Vojtech Juranek <vjuranek(a)redhat.com&gt; >> > wrote: >> > >> > > >> > > >> > > >> > > Hi, >> > > can anybody give me a hint which component is responsible for >> > > installing >> > > host >> >> when I add a host in engine UI? Or how to change vdsm version >> >> > > installed this way on the host? >> > > >> > > >> > > >> > > >> > > >> > > It installs vdsm-4.40.2: >> > > >> > > >> > > >> > > >> > > >> > > [root@localhost ~]# rpm -q ovirt-release44-pre >> > > ovirt-release44-pre-4.4.0-0.11.beta4.el8.noarch >> > >> > >> > >> > >> > Remove this package and follow the instructions here: >> > https://github.com/ovirt/vdsm#manual-installation >> >> >> >> I know how to fix it on my env. I want to fix in appropriate ovirt >> component

>> release.> > > > I'm not sure about the semantics of 4.4.pre, but project version is > configured

> https://gerrit.ovirt.org/#/admin/projects/releng-tools > > > > This is the last patch adding vdsm: > https://gerrit.ovirt.org/#/c/108276/ > > > > Typically the maintainer responsible for the builds is updating > the version for every release. Looks like vdsm 3.40.13 is missing. The subject of the patch above is wrong (copy & paste error), it actually adds v4.40.13. This version is also available on ovirt.org in master and pre-4.4.

The maintainer adds each release to releng-tools when a build is done (unless it's superseded by another build immediately) and the build team is kind enough to ping him in case he doesn't. :-) > To add it you need to find the on_merge job for last tag which seems to > be: > > > commit 3928f7f08287885fd248af08b16379476504e5be (tag: v4.40.13) > Author: Milan Zamazal <mzamazal(a)redhat.com&gt; > Date: Tue Apr 7 14:35:03 2020 +0200 > > > > New release: 4.40.13 > > > > You can find it here: > https://gerrit.ovirt.org/c/108275/#message-473c8b04_5a25626e > > > > Based on this you can prepare a patch. > > > > It would be nice if we can automate this process to avoid the manual > steps. > > >> > > [root@localhost ~]# rpm -q vdsm >> > > vdsm-4.40.2-1.el8.x86_64 >> > > >> > > >> > > >> > > >> > > >> > > We need newer version of vdsm (at least 4.40.11) to work properly >> > > with >> > > imageio >> >> 2.0. >> >> > > >> > > >> > > >> > > >> > > vdsm 4.40.13 can be pushed by running dnf update, but it's not very >> > > user >> > > friendly (moreover imageio service needs to be restarted after update >> > > and >> > > it's >> >> not obvious for the user t do so), so I'd like to change it to >> >> > > install 4.40.13 automatically when installing all other ovirt stuff. >> > > >> > > >> > > >> > > >> > > >> > > Thanks >> > > Vojta >> > >> > >> > >> > _______________________________________________ >> > Devel mailing list -- devel(a)ovirt.org >> > To unsubscribe send an email to devel-leave(a)ovirt.org >> > Privacy Statement: https://www.ovirt.org/privacy-policy.html >> > oVirt Code of Conduct: >> > https://www.ovirt.org/community/about/community-guidelines/ List >> > Archives: >> > https://lists.ovirt.org/archives/list/devel@ovirt.org/message/XP6RHEKW4 >> > 36PX

>> >> _______________________________________________ Devel mailing list -- devel(a)ovirt.org To unsubscribe send an email to devel-leave(a)ovirt.org Privacy Statement: https://www.ovirt.org/privacy-policy.html oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ List Archives: https://lists.ovirt.org/archives/list/devel@ovirt.org/message/YMK4AGVFV3JG6 FBAQTHWFRLWNKDEHF55/