Red Hat Bugzilla – Bug 978250
Anaconda does not ignore/timeout non-fatal warning
Last modified: 2017-04-04 16:45:56 EDT
Description of problem:
Kickstart installation is stopped by non-fatal interactive dialog in case of read-only disk. In the past it was requested by customer to avoid such dialogs in kickstart installations via Bug 455465.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
Prepare the system with read-only disc drive (SD card with write protection for example)
or with libvirt (virt-manager):
When setting up machine, check "Customize configuration before install"
Add additional disk and mark it readonly
or with qemu:
prepare 2 disk images:
qemu-img create disk1.img 10G
qemu-img create disk2.img 1G
get boot.iso for tested compose
run: losetup -r /dev/loopN disk2.img
qemu-kvm -monitor stdio -m 1024 -net tap -net nic,model=virtio -drive if=virtio,file=disk1.img,boot=on -drive if=virtio,file=/dev/loopN -cdrom boot.iso -boot d
Start automated installation using autopart specified in kickstart
Warning dialog blocking the kickstart execution
Installation finished without user's intervention
This seems to be a regression to Bug 455465
Created attachment 765443 [details]
Created attachment 765444 [details]
Created attachment 765445 [details]
Created attachment 765446 [details]
Marian, this does not seem to be bug because if qemu-kvm is run with parameter
where /dev/loopN is mounted readonly, the virtual system has no information about read only property until it tries to write to block device. The proper way how to handle this is to append readonly parameter to aforementioned line,
Note that readonly parameter works on hypervisor running RHEL6 or newer.
If you want to know whether the system sees some drive as readonly you can verify it by running the following command
blockdev --getro /dev/sda
I have updated the test case. I'm sorry that I forgot to do that earlier.
I've just tried to run several installations on various virtual machines with readonly disks and didn't see the dialog. Marian, can you please retest this issue?
Red Hat Enterprise Linux 5 shipped it's last minor release, 5.11, on September 14th, 2014. On March 31st, 2017 RHEL 5 exits Production Phase 3 and enters Extended Life Phase. For RHEL releases in the Extended Life Phase, Red Hat will provide limited ongoing technical support. No bug fixes, security fixes, hardware enablement or root-cause analysis will be available during this phase, and support will be provided on existing installations only. If the customer purchases the Extended Life-cycle Support (ELS), certain critical-impact security fixes and selected urgent priority bug fixes for the last minor release will be provided. The specific support and services provided during each phase are described in detail at http://redhat.com/rhel/lifecycle
This BZ does not appear to meet ELS criteria so is being closed WONTFIX. If this BZ is critical for your environment and you have an Extended Life-cycle Support Add-on entitlement, please open a case in the Red Hat Customer Portal, https://access.redhat.com ,provide a thorough business justification and ask that the BZ be re-opened for consideration of an errata. Please note, only certain critical-impact security fixes and selected urgent priority bug fixes for the last minor release can be considered.