Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.
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.

Bug 1477984

Summary: DUD kmod package has installed conflicts with yourself
Product: Red Hat Enterprise Linux 7 Reporter: Petr Oros <poros>
Component: yumAssignee: Valentina Mukhamedzhanova <vmukhame>
Status: CLOSED CURRENTRELEASE QA Contact: BaseOS QE Security Team <qe-baseos-security>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 7.5CC: emrakova, james.antill
Target Milestone: rc   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2018-06-29 09:18:29 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Petr Oros 2017-08-03 12:03:29 UTC
Description of problem:

We have kmod-VENDOR-MODULE packages created by tool called ddiskit.
Our team creates a DUD to enable hardware in z-stream and hardware certification.
Every DUD produced by our team have naming convention: kmod-VENDOR-MODULE.
It is because we allow third party drivers with same name.

For example: we create kmod-redhat-e1000e
             3rd vendor create kmod-vendor-e1000e

For this case we allow only one installation for kmod-e1000e.
I resolved it in spec:
"""
Name: kmod-VENDOR-MODULE
Provides: kmod-MODULE
Conflict: kmod-MODULE
"""

I hope, it is right solution, but:

# yum check
Loaded plugins: langpacks, product-id, search-disabled-repos, subscription-manager
kmod-redhat-cxgb4-rh7_3-3.el7_3.x86_64 has installed conflicts kmod-cxgb4: kmod-redhat-cxgb4-rh7_3-3.el7_3.x86_64
# 

Package have conflict with yourself.
What now?
Fix yum (package yourself-conflict do not make any sense)
Fix kmod spec and resolve "conflict" some else?

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

How reproducible:
Install any kmod-redhat-DRIVER package.

Steps to Reproduce:
1. Install any kmod-redhat-DRIVER package.
2. Run yum check
3.

Actual results:
Package has installed conflicts with yourself

Expected results:
Package has not installed conflicts with yourself

Additional info:

Comment 3 Petr Oros 2018-06-29 09:18:29 UTC
I checked in rhel 7.5 and it works for now.