Bug 1497729
| Summary: | RHEL 7.4 does not find kickstart ks.cfg | ||||||
|---|---|---|---|---|---|---|---|
| Product: | Red Hat Enterprise Linux 7 | Reporter: | jwamsc | ||||
| Component: | anaconda | Assignee: | Anaconda Maintenance Team <anaconda-maint-list> | ||||
| Status: | CLOSED WONTFIX | QA Contact: | Release Test Team <release-test-team-automation> | ||||
| Severity: | medium | Docs Contact: | |||||
| Priority: | unspecified | ||||||
| Version: | 7.4 | CC: | giuseppe.ragusa, herrold, jkonecny, jwamsc, yvan.broccard | ||||
| Target Milestone: | rc | ||||||
| Target Release: | --- | ||||||
| Hardware: | x86_64 | ||||||
| OS: | Linux | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2021-01-15 07:42:56 UTC | Type: | Bug | ||||
| Regression: | --- | Mount Type: | --- | ||||
| Documentation: | --- | CRM: | |||||
| Verified Versions: | Category: | --- | |||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||
| Embargoed: | |||||||
| Attachments: |
|
||||||
|
Description
jwamsc
2017-10-02 14:18:27 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). Same problem confirmed on 7.5 Hello, Could you please provide us commands you are using to create the USB flash drive? 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. 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? 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). 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.
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. The needinfo request[s] on this closed bug have been removed as they have been unresolved for 500 days |