Il giorno gio 8 ago 2019 alle ore 11:20 Maton, Brett <matonb@ltresources.co.uk> ha scritto:
Sure, it seems to be running now.

For anyone else with this issue, I ended up with this addtional repo file:

cat /etc/yum.repos.d/ov4.3-fix.repo
[ovirt-4.3-fix]
name=oVirt 4.3 Pre-Release Fix CentOS 7.7
baseurl=https://buildlogs.centos.org/centos/7/virt/x86_64/ovirt-4.3/
enabled=1
gpgcheck=1
gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-ovirt-4.3

exclude=python2-sanlock


thanks, adding it to release notes for 4.3.6 rc2 here: https://github.com/oVirt/ovirt-site/pull/2067

 

On Thu, 8 Aug 2019 at 09:55, Sandro Bonazzola <sbonazzo@redhat.com> wrote:


Il giorno gio 8 ago 2019 alle ore 10:37 Maton, Brett <matonb@ltresources.co.uk> ha scritto:
Thanks Sandro,

   Run into another dependency issue though:

Resolving Dependencies
--> Running transaction check
---> Package ovirt-release43-pre.noarch 0:4.3.6-0.1.rc1.el7 will be updated
---> Package ovirt-release43-pre.noarch 0:4.3.6-0.2.rc2.el7 will be an update
---> Package python2-sanlock.x86_64 0:3.7.1-1.el7 will be obsoleting
--> Processing Dependency: sanlock-lib = 3.7.1-1.el7 for package: python2-sanlock-3.7.1-1.el7.x86_64
---> Package sanlock.x86_64 0:3.6.0-1.el7 will be updated
---> Package sanlock.x86_64 0:3.7.3-1.el7 will be an update
---> Package sanlock-lib.x86_64 0:3.6.0-1.el7 will be updated
---> Package sanlock-lib.x86_64 0:3.7.3-1.el7 will be an update
---> Package sanlock-python.x86_64 0:3.6.0-1.el7 will be obsoleted
---> Package vdsm.x86_64 0:4.30.25-1.el7 will be updated
---> Package vdsm.x86_64 0:4.30.26-1.el7 will be an update
--> Processing Dependency: sanlock-python >= 3.7.3 for package: vdsm-4.30.26-1.el7.x86_64
---> Package vdsm-api.noarch 0:4.30.25-1.el7 will be updated
---> Package vdsm-api.noarch 0:4.30.26-1.el7 will be an update
---> Package vdsm-client.noarch 0:4.30.25-1.el7 will be updated
---> Package vdsm-client.noarch 0:4.30.26-1.el7 will be an update
---> Package vdsm-common.noarch 0:4.30.25-1.el7 will be updated
---> Package vdsm-common.noarch 0:4.30.26-1.el7 will be an update
---> Package vdsm-gluster.x86_64 0:4.30.25-1.el7 will be updated
---> Package vdsm-gluster.x86_64 0:4.30.26-1.el7 will be an update
---> Package vdsm-hook-ethtool-options.noarch 0:4.30.25-1.el7 will be updated
---> Package vdsm-hook-ethtool-options.noarch 0:4.30.26-1.el7 will be an update
---> Package vdsm-hook-fcoe.noarch 0:4.30.25-1.el7 will be updated
---> Package vdsm-hook-fcoe.noarch 0:4.30.26-1.el7 will be an update
---> Package vdsm-hook-openstacknet.noarch 0:4.30.25-1.el7 will be updated
---> Package vdsm-hook-openstacknet.noarch 0:4.30.26-1.el7 will be an update
---> Package vdsm-hook-vhostmd.noarch 0:4.30.25-1.el7 will be updated
---> Package vdsm-hook-vhostmd.noarch 0:4.30.26-1.el7 will be an update
---> Package vdsm-hook-vmfex-dev.noarch 0:4.30.25-1.el7 will be updated
---> Package vdsm-hook-vmfex-dev.noarch 0:4.30.26-1.el7 will be an update
---> Package vdsm-http.noarch 0:4.30.25-1.el7 will be updated
---> Package vdsm-http.noarch 0:4.30.26-1.el7 will be an update
---> Package vdsm-jsonrpc.noarch 0:4.30.25-1.el7 will be updated
---> Package vdsm-jsonrpc.noarch 0:4.30.26-1.el7 will be an update
---> Package vdsm-network.x86_64 0:4.30.25-1.el7 will be updated
---> Package vdsm-network.x86_64 0:4.30.26-1.el7 will be an update
---> Package vdsm-python.noarch 0:4.30.25-1.el7 will be updated
---> Package vdsm-python.noarch 0:4.30.26-1.el7 will be an update
---> Package vdsm-yajsonrpc.noarch 0:4.30.25-1.el7 will be updated
---> Package vdsm-yajsonrpc.noarch 0:4.30.26-1.el7 will be an update
--> Running transaction check
---> Package python2-sanlock.x86_64 0:3.7.1-1.el7 will be obsoleting
--> Processing Dependency: sanlock-lib = 3.7.1-1.el7 for package: python2-sanlock-3.7.1-1.el7.x86_64
---> Package sanlock-python.x86_64 0:3.6.0-1.el7 will be updated
---> Package sanlock-python.x86_64 0:3.7.3-1.el7 will be an update
--> Finished Dependency Resolution
Error: Package: python2-sanlock-3.7.1-1.el7.x86_64 (ovirt-4.3-fix)

3.7.1-1 shouldn't be there, it's not tagged for testing.
can you please exclude python2-sanlock in your repo file?

exclude=python2-sanlock


 
           Requires: sanlock-lib = 3.7.1-1.el7
           Removing: sanlock-lib-3.6.0-1.el7.x86_64 (@base)
               sanlock-lib = 3.6.0-1.el7
           Updated By: sanlock-lib-3.7.3-1.el7.x86_64 (ovirt-4.3-fix)
               sanlock-lib = 3.7.3-1.el7
           Available: sanlock-lib-3.7.1-1.el7.x86_64 (ovirt-4.3-fix)
               sanlock-lib = 3.7.1-1.el7
           Available: sanlock-lib-3.7.1-2.el7.x86_64 (ovirt-4.3-fix)
               sanlock-lib = 3.7.1-2.el7
           Available: sanlock-lib-3.7.1-2.1.el7.x86_64 (ovirt-4.3-fix)
               sanlock-lib = 3.7.1-2.1.el7
 You could try using --skip-broken to work around the problem
 You could try running: rpm -Va --nofiles --nodigest


On Thu, 8 Aug 2019 at 08:59, Sandro Bonazzola <sbonazzo@redhat.com> wrote:


Il giorno gio 8 ago 2019 alle ore 09:56 Maton, Brett <matonb@ltresources.co.uk> ha scritto:
I just tried to update my 4.6 testlab and got the following RPM dependency issue:

rpm -qa ovirt-release*
ovirt-release43-pre-4.3.6-0.1.rc1.el7.noarch

Error encountered:

yum upgrade
...
Error: Package: vdsm-4.30.26-1.el7.x86_64 (ovirt-4.3-pre)
           Requires: sanlock-python >= 3.7.3
           Installed: sanlock-python-3.6.0-1.el7.x86_64 (@base)
               sanlock-python = 3.6.0-1.el7
...


yes, as mentioned in release announce, this requires RHEL / CentOS 7.7.
you can workaround this by adding https://buildlogs.centos.org/centos/7/virt/x86_64/ovirt-4.3/ repo until CentOS 7.7 will be released
 


Regards,
Brett

On Thu, 8 Aug 2019 at 07:53, Sandro Bonazzola <sbonazzo@redhat.com> wrote:
The oVirt Project is pleased to announce the availability of the oVirt 4.3.6 Second Release Candidate for testing, as of August 8th, 2019.

This update is a release candidate of the sixth in a series of stabilization updates to the 4.3 series.
This is pre-release software. This pre-release should not to be used in production.

This release is available now on x86_64 architecture for:
* Red Hat Enterprise Linux 7.7 or later (but <8)
* CentOS Linux (or similar) 7.7 or later (but <8)

This release supports Hypervisor Hosts on x86_64 and ppc64le architectures for:
* Red Hat Enterprise Linux 7.7 or later (but <8)
* CentOS Linux (or similar) 7.7 or later (but <8)
* oVirt Node 4.3 (available for x86_64 only)

See the release notes [1] for installation / upgrade instructions and a list of new features and bugs fixed.

Notes:
- oVirt Appliance is already available
- oVirt Node is not yet available, pending CentOS 7.7 release to be available

Additional Resources:
* Read more about the oVirt 4.3.6 release highlights:http://www.ovirt.org/release/4.3.6/
* Get more oVirt Project updates on Twitter: https://twitter.com/ovirt
* Check out the latest project news on the oVirt blog:http://www.ovirt.org/blog/

[1] http://www.ovirt.org/release/4.3.6/

--

Sandro Bonazzola

MANAGER, SOFTWARE ENGINEERING, EMEA R&D RHV

Red Hat EMEA

sbonazzo@redhat.com   

Red Hat respects your work life balance. Therefore there is no need to answer this email out of your office hours.
_______________________________________________
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-leave@ovirt.org
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/users@ovirt.org/message/6STDS7UGBADU2IR3VUIJP4KH4YIWH4HL/


--


--


--