Dependency Resolution problem

Latest response

Hello,

When i try to install any package on rhel 7.6, i get the following dependency errors:

---> Package python-pytoml.noarch 0:0.1.14-1.git7dea353.el7 will be installed
--> Finished Dependency Resolution
Error: Package: 7:lvm2-cluster-2.02.180-8.el7.x86_64 (@Server-ResilientStorage/7.6)
Requires: lvm2 = 7:2.02.180-8.el7
Removing: 7:lvm2-2.02.180-8.el7.x86_64 (@anaconda/7.6)
lvm2 = 7:2.02.180-8.el7
Updated By: 7:lvm2-2.02.180-10.el7_6.3.x86_64 (rhel-7-server-rpms)
lvm2 = 7:2.02.180-10.el7_6.3
Available: 7:lvm2-2.02.105-14.el7.x86_64 (rhel-7-server-rpms)
lvm2 = 7:2.02.105-14.el7
Available: 7:lvm2-2.02.115-3.el7.x86_64 (rhel-7-server-rpms)
lvm2 = 7:2.02.115-3.el7
Available: 7:lvm2-2.02.115-3.el7_1.1.x86_64 (rhel-7-server-rpms)
lvm2 = 7:2.02.115-3.el7_1.1
Available: 7:lvm2-2.02.130-5.el7.x86_64 (rhel-7-server-rpms)
lvm2 = 7:2.02.130-5.el7
Available: 7:lvm2-2.02.130-5.el7_2.1.x86_64 (rhel-7-server-rpms)
lvm2 = 7:2.02.130-5.el7_2.1
Available: 7:lvm2-2.02.130-5.el7_2.2.x86_64 (rhel-7-server-rpms)
lvm2 = 7:2.02.130-5.el7_2.2
Available: 7:lvm2-2.02.130-5.el7_2.4.x86_64 (rhel-7-server-rpms)
lvm2 = 7:2.02.130-5.el7_2.4
Available: 7:lvm2-2.02.130-5.el7_2.5.x86_64 (rhel-7-server-rpms)
lvm2 = 7:2.02.130-5.el7_2.5
Available: 7:lvm2-2.02.166-1.el7.x86_64 (rhel-7-server-rpms)
lvm2 = 7:2.02.166-1.el7
Available: 7:lvm2-2.02.166-1.el7_3.1.x86_64 (rhel-7-server-rpms)
lvm2 = 7:2.02.166-1.el7_3.1
Available: 7:lvm2-2.02.166-1.el7_3.2.x86_64 (rhel-7-server-rpms)
lvm2 = 7:2.02.166-1.el7_3.2
Available: 7:lvm2-2.02.166-1.el7_3.3.x86_64 (rhel-7-server-rpms)
lvm2 = 7:2.02.166-1.el7_3.3
Available: 7:lvm2-2.02.166-1.el7_3.4.x86_64 (rhel-7-server-rpms)
lvm2 = 7:2.02.166-1.el7_3.4
Available: 7:lvm2-2.02.166-1.el7_3.5.x86_64 (rhel-7-server-rpms)
lvm2 = 7:2.02.166-1.el7_3.5
Available: 7:lvm2-2.02.171-8.el7.x86_64 (rhel-7-server-rpms)
lvm2 = 7:2.02.171-8.el7
Available: 7:lvm2-2.02.177-4.el7.x86_64 (rhel-7-server-rpms)
lvm2 = 7:2.02.177-4.el7
Available: 7:lvm2-2.02.180-10.el7_6.1.x86_64 (rhel-7-server-rpms)
lvm2 = 7:2.02.180-10.el7_6.1
Available: 7:lvm2-2.02.180-10.el7_6.2.x86_64 (rhel-7-server-rpms)
lvm2 = 7:2.02.180-10.el7_6.2


Dependency resolving failed due to missing dependencies.
Some repositories on your system are disabled, but yum can enable them
and search for missing dependencies. This will require downloading
metadata for disabled repositories and may take some time and traffic.


Enable all repositories and try again? [y/N]: y

and nothing...

Edit: I found the solution to this problem in here : https://access.redhat.com/solutions/2148301 , Seems like removing that package resolved all the problems.

Responses

You might have inconsistencies with the packages you already have installed. What you you get if you run yum check?

I found a solution to this : https://access.redhat.com/solutions/2148301 Thank you

Rachid Chami

Please confirm with us a few things here - and someone ought to chime in at some point

First, please examine this previous discussion, and scroll down to the portion that relates to RHEL 7, and see if the information there is a good fit with your issue. It seems "Resilient Storage" repo was needed for lvm2-cluster. The channel name is apparently rhel-rs-for-rhel-7-server-rpms according to https://access.redhat.com/solutions/18999 - examine this link

From that last link, attempt to see if this resolves it --> RHEL 7 with Red Hat Subscription Manager Using Red Hat Subscription Manager or subscription-manager, enable the "Resilient Storage" repository for all systems in the cluster. For example:

[root@yoursystem] # subscription-manager repos --enable=rhel-rs-for-rhel-7-server-rpms

If the above doesn't work, then examine these things... - Are you using Red Hat Enterprise Linux Server (not workstation, i would believe you're using the server edition)? - What happens when you run subscription-manager status as root on that affected system? - What happens when you view that system's subscriptions at the Red Hat portal? (what repos do you see?)

Regards

RJ

I found a solution to this : https://access.redhat.com/solutions/2148301 Thank you

Rachid Chami,

Glad you got it sorted out. I had seen that solution, but it applied to RHEL 5, and your system is RHEL 7.

Did you have a cloned channel on a Red Hat satellite?

Regardless, we're glad you got it resolved.

Regards

RJ

@RJ: your solution worked, thank you!