Il giorno ven 7 dic 2018 alle ore 10:06 Demeter Tibor <[email protected]> ha scritto:
> Dear Simon, > > It is working fine with a little bit modification. You need to use > "exclude=nbdkit-*" instead of "exclude=nbdkit*" . > > I would consider "yum update ovirt-release42" as a better option. It will provide the missing nbdkit dependency. It has been fixed in oVirt 4.2.7 release. > Thanks for your mention, > > Regards, > > Tibor > > > ----- 2018. dec.. 6., 22:37, Simon Coter <[email protected]> írta: > > Hi Tibor, > > the update is trying to install: > > nbdkit(x86-64) = 1.2.7-2.el7 > > while you only have: > > nbdkit(x86-64) = 1.2.6-1.el7_6.2 > > 1.2.7 release is available on ovirt-4.2-epel repository while 1.2.6 is > part of CentOS “Base” and “Updates”. > The problem is that "nbdkit-plugin-vddk” has only 1.2.6 release and this > depends on “ndbkit”. > Possible workaround that should work: > > Edit the <ovirt>.repo containing “ovirt-4.2-epel” and add the following > line to the “ovirt-4.2-epel” entry: > > exclude=ndbkit* > > then, rerun the update. > > Simon > > On Dec 6, 2018, at 10:27 PM, Demeter Tibor <[email protected]> wrote: > > Dear Roberto, > > Thank you for your reply. > I would like to upgrade the node os (not just ovirt) to latest (7.6) > version. > Thanks > > Regards, > > Tibor > > > > ----- 2018. dec.. 6., 21:39, Roberto Nunin <[email protected]> írta: > > Hi > > I had a similar problem just yesterday. > I've disabled all three sources within CentOS-Base.repo. > > My nodes are still 7.5, but hope that this can help anyway. > My update process, done from hested-engine gui, has completed after the > change. > > BR > > > > Il giorno gio 6 dic 2018 alle 20:19 Demeter Tibor <[email protected]> > ha scritto: > >> Dear All, >> I would like to upgrade my ovirt 4.2.5 to 4.2.7. >> >> The hosted engine upgrade was success, but on the nodes i've got an >> dependency error: >> >> ---> Package mesa-libgbm.x86_64 0:18.0.5-3.el7 will be installed >> --> Processing Dependency: mesa-libglapi = 18.0.5-3.el7 for package: >> mesa-libgbm-18.0.5-3.el7.x86_64 >> --> Processing Dependency: libwayland-server.so.0()(64bit) for package: >> mesa-libgbm-18.0.5-3.el7.x86_64 >> ---> Package nbdkit.x86_64 0:1.2.7-2.el7 will be installed >> ---> Package nbdkit-plugin-python2.x86_64 0:1.2.7-2.el7 will be installed >> --> Processing Dependency: nbdkit-plugin-python-common = 1.2.7-2.el7 for >> package: nbdkit-plugin-python2-1.2.7-2.el7.x86_64 >> ---> Package nbdkit-plugin-vddk.x86_64 0:1.2.6-1.el7_6.2 will be installed >> --> Processing Dependency: nbdkit(x86-64) = 1.2.6-1.el7_6.2 for package: >> nbdkit-plugin-vddk-1.2.6-1.el7_6.2.x86_64 >> ---> Package python2-blockdev.x86_64 0:2.18-3.el7 will be installed >> ---> Package python2-futures.noarch 0:3.1.1-5.el7 will be installed >> --> Running transaction check >> ---> Package libwayland-server.x86_64 0:1.15.0-1.el7 will be installed >> ---> Package mesa-libglapi.x86_64 0:18.0.5-3.el7 will be installed >> ---> Package nbdkit-plugin-python-common.x86_64 0:1.2.7-2.el7 will be >> installed >> ---> Package nbdkit-plugin-vddk.x86_64 0:1.2.6-1.el7_6.2 will be installed >> --> Processing Dependency: nbdkit(x86-64) = 1.2.6-1.el7_6.2 for package: >> nbdkit-plugin-vddk-1.2.6-1.el7_6.2.x86_64 >> --> Finished Dependency Resolution >> --> Running transaction check >> ---> Package kernel.x86_64 0:3.10.0-693.11.6.el7 will be erased >> ---> Package nbdkit-plugin-vddk.x86_64 0:1.2.6-1.el7_6.2 will be installed >> --> Processing Dependency: nbdkit(x86-64) = 1.2.6-1.el7_6.2 for package: >> nbdkit-plugin-vddk-1.2.6-1.el7_6.2.x86_64 >> --> Finished Dependency Resolution >> Error: Package: nbdkit-plugin-vddk-1.2.6-1.el7_6.2.x86_64 (updates) >> Requires: nbdkit(x86-64) = 1.2.6-1.el7_6.2 >> Available: nbdkit-1.2.6-1.el7.x86_64 (base) >> nbdkit(x86-64) = 1.2.6-1.el7 >> Available: nbdkit-1.2.6-1.el7_6.2.x86_64 (updates) >> nbdkit(x86-64) = 1.2.6-1.el7_6.2 >> Installing: nbdkit-1.2.7-2.el7.x86_64 (ovirt-4.2-epel) >> nbdkit(x86-64) = 1.2.7-2.el7 >> You could try using --skip-broken to work around the problem >> You could try running: rpm -Va --nofiles --nodigest >> >> >> How can I solve this? >> >> Thanks in advance, >> >> Regards, >> >> Tibor >> >> >> _______________________________________________ >> Users mailing list -- [email protected] >> To unsubscribe send an email to [email protected] >> Privacy Statement: https://www.ovirt.org/site/privacy-policy/ >> oVirt Code of Conduct: >> https://www.ovirt.org/community/about/community-guidelines/ >> List Archives: >> https://lists.ovirt.org/archives/list/[email protected]/message/AUAO3LNG2LY56K37ARWH6ORSC6MZL5CA/ >> > -- > Roberto Nunin > > > > _______________________________________________ > Users mailing list -- [email protected] > To unsubscribe send an email to [email protected] > Privacy Statement: https://www.ovirt.org/site/privacy-policy/ > oVirt Code of Conduct: > https://www.ovirt.org/community/about/community-guidelines/ > List Archives: > https://lists.ovirt.org/archives/list/[email protected]/message/BH6UKVHFNACOQV7Y7YWCV2YP54SUQJJQ/ > > > > _______________________________________________ > Users mailing list -- [email protected] > To unsubscribe send an email to [email protected] > Privacy Statement: https://www.ovirt.org/site/privacy-policy/ > oVirt Code of Conduct: > https://www.ovirt.org/community/about/community-guidelines/ > List Archives: > https://lists.ovirt.org/archives/list/[email protected]/message/T6LM7JF6UYJTERUJA7EJRHL35Z6GDOOU/ > -- SANDRO BONAZZOLA MANAGER, SOFTWARE ENGINEERING, EMEA R&D RHV Red Hat EMEA <https://www.redhat.com/> [email protected] <https://red.ht/sig>
_______________________________________________ Users mailing list -- [email protected] To unsubscribe send an email to [email protected] Privacy Statement: https://www.ovirt.org/site/privacy-policy/ oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ List Archives: https://lists.ovirt.org/archives/list/[email protected]/message/IVGTTWNV6G52HDDWBLVCHKJ27WFQ6Z3P/
