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.
Description of problem:
If during installation you try to install a module that depends on non-default
stream of another module the installation fails with conflict because the default
stream is also active.
Version-Release number of selected component (if applicable):
RHEL-9.0.0-20220111.1
anaconda 34.25.0.23-1.el9
How reproducible:
Always
Steps to Reproduce:
Start installation with following kickstart:
repo --name modilarity_repo --install --baseurl {TEST_REPO_URL}
%packages
# tr-modular:legacy depends on tr-dependency:10 but tr-dependency:20 is default stream
@tr-modular:legacy
%end
zerombr
clearpart --all --initlabel
autopart
timezone Europe/Prague --isUtc
keyboard us
lang en_US.UTF-8
Actual results:
Error in installer:
Problems in request:
Modular dependency problems with Defaults:
Problem: module tr-modular:legacy:1:.noarch requires module(tr-dependency:10), but none of the providers can be installed
- module tr-dependency:10:1:.noarch conflicts with module(tr-dependency) provided by tr-dependency:20:2:.noarch
- module tr-dependency:20:2:.noarch conflicts with module(tr-dependency) provided by tr-dependency:10:1:.noarch
- conflicting requests
Some packages, groups or modules are broken, the installation will be aborted.
Expected results:
Installation finishes without problems,
@tr-modular:legacy and @tr-dependency:10 are installed
Comment 10RHEL Program Management
2023-07-19 07:28:15 UTC
After evaluating this issue, there are no plans to address it further or fix it in an upcoming release. Therefore, it is being closed. If plans change such that this issue will be fixed in an upcoming release, then the bug can be reopened.
Description of problem: If during installation you try to install a module that depends on non-default stream of another module the installation fails with conflict because the default stream is also active. Version-Release number of selected component (if applicable): RHEL-9.0.0-20220111.1 anaconda 34.25.0.23-1.el9 How reproducible: Always Steps to Reproduce: Start installation with following kickstart: repo --name modilarity_repo --install --baseurl {TEST_REPO_URL} %packages # tr-modular:legacy depends on tr-dependency:10 but tr-dependency:20 is default stream @tr-modular:legacy %end zerombr clearpart --all --initlabel autopart timezone Europe/Prague --isUtc keyboard us lang en_US.UTF-8 Actual results: Error in installer: Problems in request: Modular dependency problems with Defaults: Problem: module tr-modular:legacy:1:.noarch requires module(tr-dependency:10), but none of the providers can be installed - module tr-dependency:10:1:.noarch conflicts with module(tr-dependency) provided by tr-dependency:20:2:.noarch - module tr-dependency:20:2:.noarch conflicts with module(tr-dependency) provided by tr-dependency:10:1:.noarch - conflicting requests Some packages, groups or modules are broken, the installation will be aborted. Expected results: Installation finishes without problems, @tr-modular:legacy and @tr-dependency:10 are installed