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 1748365 - dnf --releasever=/ option does not work
Summary: dnf --releasever=/ option does not work
Keywords:
Status: CLOSED DUPLICATE of bug 1699348
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: dnf
Version: 8.0
Hardware: Unspecified
OS: Unspecified
medium
unspecified
Target Milestone: rc
: 8.0
Assignee: Jaroslav Mracek
QA Contact: BaseOS QE Security Team
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-09-03 12:39 UTC by Lukas Herbolt
Modified: 2020-05-05 18:49 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-09-27 08:29:12 UTC
Type: Bug
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Lukas Herbolt 2019-09-03 12:39:36 UTC
Description of problem:
When preparing diskless machine, following command is failing;

# dnf install @Base kernel dracut-network nfs-utils --installroot=/nfs/exported/machine/ --releasever=/
 

Version-Release number of selected component (if applicable):
RHEL 8
dnf-4.0.9.2-5.el8.noarch

How reproducible:
Every time 


Steps to Reproduce:
1. create directory to perform chroot install 
mkdir /nfs/exported/machine/
2. run:
# dnf install @Base kernel dracut-network nfs-utils --installroot=/nfs/exported/machine/ --releasever=/


Actual results:
instalation fails, complaining about /nfs/exported/machine/etc/os-release
does not exists

Expected results:
it will work as on RHEL 7

Additional info:
workaround 
# mkdir /nfs/exported/machine/etc
# cp -s /etc/os-release /nfs/exported/machine/etc/os-release

Comment 1 Jaroslav Mracek 2019-09-16 17:47:18 UTC
I believe that the problem is not related to --releasever option but to detection of module_platform_id. The issue was fixed by https://github.com/rpm-software-management/libdnf/commit/add998a2afabead4beaeeb91727a5389d7d5a859 that is part of libdnf-0.31.0.

Please is the issue related to me suggestion?

For testing purpose I can provide a build of libdnf with other component with patch mentioned above.

Comment 2 Jaroslav Mracek 2019-09-27 08:29:12 UTC
I suggest that the issue is resolved by patch mentioned above, therefore marking the bug as a duplicate.

*** This bug has been marked as a duplicate of bug 1699348 ***


Note You need to log in before you can comment on or make changes to this bug.