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.
Using a driver disk for a 7.2 alpha installation fails. The problem is seen with
different installation methods (pxe/net or remote storage).
How reproducible: always
Steps to Reproduce:
1. install 7.2 alpha
2. select a driver disk
Actual results:
A fatal error screen (see screenshot1) about a missing kmod-driver package appears.
The installation will be aborted, but the driver package is still present and usable (see screenshot2).
Expected results:
Driver disk should be loaded and installed
Additional info:
No additional information is available is collectable because no shell (F2) or F3 screen is working.
The driver package can be installed on an existing 7.2 system without problems.
Thanks for reporting this.
From the kmod package it seems like you have rebuild the driver for rhel7.2, I understand it can be loaded/used on an existing rhel7.2 installation.
- Can you upload the driver package?
- Also the one for 7.1 might be useful, so I can compare with a 7.1 deployment.
- When using pxeboot, you use format "dd=http://<ip>/driverdisk.img", right?
Danke Peter.
I got the issue reproduced, and this looks indeed like an issue here preventing the DUD to work.
- For reproducing, I used KVM guests, deployed with virt-install
- I use kickstart, and the additionally inst.dd=http://<ip>/driverdisk.img
- After 7.1 deployment, kmod-megasr is installed, after 7.2 deployment not
- both DUD images follow the same directory structure
- the 7.2 RPM installs fine on an installed rhel7.2 alpha
I see this difference while installation, RHEL7.1, but not 7.2:
DD: Processing Network Drivers from /tmp/DD-net/
DD: Processing DD repo /media/DD//rpms/x86_64 on /tmp/DD-net/megasr-16.01.2014.0318.4fts-6.el7.1-000.x86_64.iso
DD: Extracting files from /media/DD//rpms/x86_64/kmod-megasr-16.01.2014.0318.4fts-6.el7.1.x86_64.rpm
This issue should be considered as blocker.
We're trying to reproduce the problem(s) now.
Note that the original problem in comment #0 and the problem in comment #8 are two different failures in two different code paths, so we may need to split this bug in two in order to track those separately.
I can reproduce this in KVM when booting with the provided 7.2 DUD iso. There are multiple problems, here are fixes for 2 of them:
https://github.com/rhinstaller/anaconda/pull/337
In addition to those it extracts the drivers 3 times, into DD-1, DD-2 and DD-3.
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://rhn.redhat.com/errata/RHBA-2015-2284.html