|Summary:||unable to install module content into nonstandard install root|
|Product:||Red Hat Enterprise Linux 8||Reporter:||Martin Kyral <mkyral>|
|Component:||dnf||Assignee:||Jaroslav Mracek <jmracek>|
|Status:||CLOSED ERRATA||QA Contact:||Eva Mrakova <emrakova>|
|Version:||8.0||CC:||dmach, emrakova, james.antill, jmracek, ksrot, mcermak, mschena, zhilli|
|Fixed In Version:||libdnf-0.33.0-1.el8||Doc Type:||If docs needed, set a value|
|Doc Text:||Story Points:||---|
|Last Closed:||2019-11-05 22:21:13 UTC||Type:||Bug|
|oVirt Team:||---||RHEL 7.3 requirements from Atomic Host:|
|Cloudforms Team:||---||Target Upstream Version:|
|Bug Depends On:||1681084|
Description Martin Kyral 2019-02-19 07:37:10 UTC
Comment 1 Martin Kyral 2019-02-19 10:12:22 UTC
I was instructed that there is --setopt=module_platform_id=platform:el8 option allowing instalation of modularized content into install root. Tried, tested - it works. It is documented but the mention is hidden in the huge man page. So hint in case of this failure (similar to --allowerasing / --skip-broken hints in case of package transaction problem) could help a great deal and would be enough as a fix for this bug.
Comment 2 Jaroslav Mracek 2019-03-12 18:16:42 UTC
I created a patch (https://github.com/rpm-software-management/dnf/pull/1355) that provides a hint how to set up the platform module.
Comment 3 Jaroslav Mracek 2019-06-10 10:06:17 UTC
I believe that the issue is solved by changed detection of module_platform_id. Now it is taken from available package that provides a system-release.
Comment 7 Karel Srot 2019-08-21 14:23:04 UTC
(In reply to Jaroslav Mracek from comment #3) > I believe that the issue is solved by changed detection of > module_platform_id. Now it is taken from available package that provides a > system-release. Hi Jarda, could you please provide more details on how this is supposed to work? Thank you.
Comment 8 Karel Srot 2019-08-21 14:38:17 UTC
Found the answer here https://github.com/rpm-software-management/libdnf/pull/712 However bug 1698942 is not fixed and thus the detection capabilities are limited.
Comment 10 errata-xmlrpc 2019-11-05 22:21:13 UTC
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHSA-2019:3583