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 1497729 - RHEL 7.4 does not find kickstart ks.cfg
Summary: RHEL 7.4 does not find kickstart ks.cfg
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: anaconda
Version: 7.4
Hardware: x86_64
OS: Linux
unspecified
medium
Target Milestone: rc
: ---
Assignee: Anaconda Maintenance Team
QA Contact: Release Test Team
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-10-02 14:18 UTC by jwamsc
Modified: 2023-09-15 00:04 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2021-01-15 07:42:56 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)
7.5 logs with OEMDRV-labeled virtual floppy (9.13 MB, application/x-gzip)
2018-11-18 01:15 UTC, Giuseppe Ragusa 		no flags Details
View All

Description jwamsc 2017-10-02 14:18:27 UTC 
Description of problem:
RHEL 7.4 does not find kickstart for automated installation.


Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1. Create fat32 volume labeled OEMDRV with kickstart file ks.cfg. Insert in target system.
2. Install rhel-server-7.3-x86_64-dvd.iso on USB thumb drive, and boot thumb drive. RHEL-7.3 finds and invokes OEMDRV ks.cfg. This is expected behavior.
3. Install rhel-server-7.4-x86_64-dvd.iso on USB thumb drive, and boot thumb drive, with the same OEMDRV. RHEL-7.3 does not invoke OEMDRV ks.cfg.

Actual results:
RHEL-7.4 does not invoke OEMDRV ks.cfg


Expected results:
RHEL-7.4 does invoke OEMDRV ks.cfg

Additional info:
Expected behavior: 
https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/7/html/installation_guide/sect-kickstart-howto#sect-kickstart-installation-starting
Comment 2 Yvan Broccard 2018-01-10 13:45:09 UTC 
I confirm, same behaviour.

I was able to kickstart my machines with RH7.3, and not anymore with 7.4, providing a floppy image with label OEMDRV, containing the storage drivers and a kickstart file (ks.cfg).
Comment 3 Giuseppe Ragusa 2018-11-01 22:37:16 UTC 
Same problem confirmed on 7.5
Comment 4 Jiri Konecny 2018-11-02 08:55:26 UTC 
Hello,

Could you please provide us commands you are using to create the USB flash drive?
Comment 5 Giuseppe Ragusa 2018-11-02 12:12:28 UTC 
Sure.

16 GiB USB flash drive (previously used as boot disk for installations)

From Linux (drive connected as sdb but not mounted):

dd if=/dev/zero of=/dev/sdb bs=1M count=100

kpartx -v -u /dev/sdb

mkfs.vfat -v -I -n OEMDRV /dev/sdb

From Windows 10 1803 x64 (drive appeared perfectly under File Explorer):

Copied kickstart file and renamed as ks.cfg

Please note that my testing was performed on a UEFI VMware vm and that Anaconda logs reported that a OEMDRV disk was found, but nonetheless interactive graphical installation started.

Many thanks.
Comment 6 Jiri Konecny 2018-11-05 10:37:27 UTC 
Thank you for this information.

Could you please start the installation with 'rd.debug' and 'inst.debug' kernel boot parameters and give us output of the console?
Comment 7 Giuseppe Ragusa 2018-11-08 20:07:00 UTC 
Sorry for the delay in replying: I had to recreate the testing environment from scratch (the physical USB drive remained the same).

I tried reproducing again the problem with a USB drive but I was not able to do so.

I confirm that a physical USB3 drive VFAT formatted and given the OEMDRV label works with 7.5 under VMware (Windows 10 1803 x64 host) both with a BIOS and a UEFI vm (USB3 physical drive inserted in a physical USB3 port and vm configured with USB virtual controller in USB 3.0 compatibility mode).

I will try to understand whether the following variables could influence the outcome in the USB case:

1) whether the physical USB port is USB3 or USB2

2) whether the virtual USB controller is in USB 2.0 or 3.0 compatibility mode


I will also try to reproduce the problem using a virtual floppy (VFAT floppy image).
Comment 8 Giuseppe Ragusa 2018-11-18 01:15:57 UTC 
Created attachment 1506849 [details]
7.5 logs with OEMDRV-labeled virtual floppy

Tested 7.5 with an OEMDRV-labeled vfat virtual floppy (under VMware Player).
Started installation from DVD menu, adding "rd.debug inst.debug" on kernel commandline.

Floppy image contained a ks.cfg kickstart file.

Floppy apparently not even accessed and installation started graphical/interactive.

Same results also with 7.3 and 7.0 installation DVDs.
Comment 10 RHEL Program Management 2021-01-15 07:42:56 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.
Comment 11 Red Hat Bugzilla 2023-09-15 00:04:15 UTC 
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 500 days
Note You need to log in before you can comment on or make changes to this bug.