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
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.