Bug 978250
| Summary: | Anaconda does not ignore/timeout non-fatal warning | ||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Product: | Red Hat Enterprise Linux 5 | Reporter: | Marian Ganisin <mganisin> | ||||||||||
| Component: | anaconda | Assignee: | Vratislav Podzimek <vpodzime> | ||||||||||
| Status: | CLOSED WONTFIX | QA Contact: | Release Test Team <release-test-team-automation> | ||||||||||
| Severity: | high | Docs Contact: | |||||||||||
| Priority: | unspecified | ||||||||||||
| Version: | 5.10 | CC: | atodorov, dcantrell, ljozsa, lmiksik, mganisin, ovasik | ||||||||||
| Target Milestone: | rc | Keywords: | Regression | ||||||||||
| Target Release: | --- | ||||||||||||
| Hardware: | Unspecified | ||||||||||||
| OS: | Unspecified | ||||||||||||
| Whiteboard: | |||||||||||||
| Fixed In Version: | Doc Type: | Known Issue | |||||||||||
| Doc Text: |
If a read-only disk is present, installation of Red Hat Enterprise Linux 5 can be interrupted by an interactive warning dialog window, and thus blocking automated installations.
|
Story Points: | --- | ||||||||||
| Clone Of: | Environment: | ||||||||||||
| Last Closed: | 2017-04-04 20:45: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: | |||||||||||||
| Bug Depends On: | |||||||||||||
| Bug Blocks: | 965983 | ||||||||||||
| Attachments: |
|
||||||||||||
|
Description
Marian Ganisin
2013-06-26 08:00:32 UTC
Created attachment 765443 [details]
anaconda.log
Created attachment 765444 [details]
ks.cfg
Created attachment 765445 [details]
syslog
Created attachment 765446 [details]
screenshot
Marian, this does not seem to be bug because if qemu-kvm is run with parameter -drive if=virtio,file=/dev/loopN 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, -drive if=virtio,file=/dev/loopN,readonly 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. |