RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Description of problem:

With the repos below, this fails:

yum install rhevm{,-dwh,-reports}

While this works:

yum install rhevm{,-dwh,-reports} java-1.7.0

I'd expect yum to be able to find this solution (use java-1.7.0) by itself, without me adding a "hint".

Version-Release number of selected component (if applicable):

yum-3.2.29-69.el6.noarch

How reproducible:

Always

Steps to Reproduce:
1. Install rhel6 with the below repos
2. yum install rhevm{,-dwh,-reports}
3.

Actual results:

Fails

Expected results:

Succeeds

Additional info:

See above. See also bug 1322528 and bug 1303132.

Repos used:

[rhel-67]
name=RHEL_67
baseurl=http://download.eng.tlv.redhat.com/pub/rhel/released/RHEL-6/6.7/Server/x86_64/os/Server/
enabled=1
gpgcheck=0

[rhel-67-optional]
name=RHEL_67_OPTIONAL
baseurl=http://download.eng.tlv.redhat.com/pub/rhel/released/RHEL-6/6.7/Server/optional/x86_64/os/
enabled=1
gpgcheck=0

[rhel-67-zstream]
name=RHEL_67_Z
baseurl=http://download.devel.redhat.com/rel-eng/repos/RHEL-6.7-Z/x86_64/
enabled=1
gpgcheck=0

[rhel-67-suppl]
name=RHEL_67_SUPPL
baseurl=http://download.devel.redhat.com/released/RHEL-6-Supplementary/6.7/Server/x86_64/os/
enabled=1
gpgcheck=0

[jboss-eap-6.4.Z]
name=jboss eap 6.4.Z
baseurl=http://download.eng.tlv.redhat.com/pub/rhel/devel/candidates/JBEAP/composing/latest-JBEAP-6.4-RHEL-6/compose/Server/x86_64/os/
enabled=1
gpgcheck=0
[rhev-3.6.5-1]
name=RHEV 3.6.5-1
baseurl=http://bob.eng.lab.tlv.redhat.com/builds/3.6/3.6.5-1/el$releasever
enabled=1
skip_if_unavailable=1
gpgcheck=0

*** Bug 1322528 has been marked as a duplicate of this bug. ***

Indeed yum's depsolver doesn't always find a solution where it exists. This will be addressed in dnf where the depsolver has a completely different algorithm. I'm afraid, on RHEL6 we will have to work around this with hints.