Il giorno mar 21 apr 2020 alle ore 13:59 Vojtech Juranek <
[email protected]> ha scritto:

> On úterý 21. dubna 2020 12:50:46 CEST Milan Zamazal wrote:
> > Vojtech Juranek <[email protected]> writes:
> >
> >
> > > On úterý 21. dubna 2020 10:56:59 CEST Milan Zamazal wrote:
> > >
> > >> Nir Soffer <[email protected]> writes:
> > >>
> > >
> > >
> > >
> > >>
> > >>
> > >> > On Mon, Apr 20, 2020 at 11:34 PM Vojtech Juranek <
> [email protected]>
> > >> > 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
> > >> >> > <[email protected]>
> > >> >> > 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
> > >
> > >  so that correct vdsm version is installed in next 4.4.pre
> > >
> > >> >> release.>
> > >> >
> > >> >
> > >> >
> > >> >
> > >> > I'm not sure about the semantics of 4.4.pre, but project version is
> > >> > configured
> > >
> > >  using releng-tools project:
> > >
> > >> > 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.
> > >
> > >
> > >
> > > correct, but installed vdsm version is 4.40.2, so any idea what's
> wrong?
> >
> >
> > No idea.  Sandro, Dafna, do you know?
>
>
> either it's relevant only for CentOS 8.1 or it was some temporal glitch,
> now I
> added new FC-30 in the same way and everything looks good (vdsm is 4.40.13
> and
> imageio runs fine)
>

Node build based on CentOS 8.1 and 4.4.0 beta 4
has vdsm-4.40.13-1.el8.x86_64
https://jenkins.ovirt.org/job/ovirt-node-ng-image_master_build-artifacts-el8-x86_64/197/artifact/exported-artifacts/ovirt-node-ng-image.manifest-rpm
so on a clean install 4.40.13 should land on your system.

If this happens again please copy / paste the yum install output so we can
try to understand which dependency broke the dependency tree.






>
> >
> > > (btw: it seems it already starts to cause trouble to other people, see
> > > Kaustav's question "Unable to add vdsm host to ovirt-engine" from
> today on
> > >
>  this ML - it seems that this is exactly same issue I spotted yesterday)>
> > >
> > >
> > >> 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 <[email protected]>
> > >> > 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 -- [email protected]
> > >> >> > To unsubscribe send an email to [email protected]
> > >> >> > 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/[email protected]/message/XP6RHE
> > >> >> > KW4
> > >> >> > 36PX
> > >
> > >  43BHCT4WYL4ZNULYR3N/
> > >
> > >> >>
> > >> >>
> > >>
> > >>
> > >> _______________________________________________
> > >> Devel mailing list -- [email protected]
> > >> To unsubscribe send an email to [email protected]
> > >> 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/[email protected]/message/YMK4AGVFV3J
> > >> G6
>  FBAQTHWFRLWNKDEHF55/
> >
> > _______________________________________________
> > Devel mailing list -- [email protected]
> > To unsubscribe send an email to [email protected]
> > 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/[email protected]/message/FANQTVMOQRNHH
> > 4XZ2V2SDRHO3TIT44EC/
>
>

-- 

Sandro Bonazzola

MANAGER, SOFTWARE ENGINEERING, EMEA R&D RHV

Red Hat EMEA <https://www.redhat.com/>

[email protected]
<https://www.redhat.com/>*
<https://www.redhat.com/en/summit?sc_cid=7013a000002D2QxAAK>*
*Red Hat respects your work life balance. Therefore there is no need to
answer this email out of your office hours.
<https://mojo.redhat.com/docs/DOC-1199578>*
_______________________________________________
Devel mailing list -- [email protected]
To unsubscribe send an email to [email protected]
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/[email protected]/message/KGJABIU3BXXQMXM2TABNJZEDHU3VHVI5/

Reply via email to