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 1769456 - Cannot add iso on local partition as installation source in TUI
Summary: Cannot add iso on local partition as installation source in TUI
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: anaconda
Version: 8.1
Hardware: x86_64
OS: Linux
medium
unspecified
Target Milestone: beta
: 8.2
Assignee: Anaconda Maintenance Team
QA Contact: Release Test Team
URL:
Whiteboard:
Depends On:
Blocks: 1743676
TreeView+ depends on / blocked
 
Reported: 2019-11-06 16:39 UTC by Petr Janda
Modified: 2021-05-06 07:30 UTC (History)
0 users

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2021-05-06 07:30:26 UTC
Type: Bug
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Petr Janda 2019-11-06 16:39:16 UTC
Description of problem:

It is not possible to add iso file stored on HDD as installation source in TUI
anaconda states that "No mountable devices found"

Version-Release number of selected component (if applicable):
RHEL-8.1.0-20191015.0
anaconda 29.19.1.13-1.el8

How reproducible:
always

Steps to Reproduce:
1. obtain machine with two HDD
2. on the sdb create two partitions, format them as ext4 
3. store boot.iso on /dev/sdb1, store dvd.iso on /dev/sdb2
4. start new text installation without network with inst.stage2=hd:/dev/sdb1:/
5. advance to "installation destination" spoke, choose only sda as installation target, choose using all space and automatic partitioning
6. try to set installation source to iso file stored on sdb2

Actual results:
anaconda states that "No mountable devices found", no way how to access dvd.iso stored on sdb2

Expected results:
iso image can be chosen as installation source

Additional info:
Workaround: set ISO file source up before destination is set

Comment 1 Petr Janda 2019-11-06 16:42:45 UTC
Created attachment 1633375 [details]
anaconda.log

Comment 2 Petr Janda 2019-11-06 16:46:37 UTC
Created attachment 1633377 [details]
ifcfg.log

Comment 3 Petr Janda 2019-11-06 16:46:45 UTC
Created attachment 1633379 [details]
lvm.log

Comment 4 Petr Janda 2019-11-06 16:46:48 UTC
Created attachment 1633380 [details]
packaging.log

Comment 5 Petr Janda 2019-11-06 16:46:52 UTC
Created attachment 1633381 [details]
program.log

Comment 6 Petr Janda 2019-11-06 16:46:56 UTC
Created attachment 1633382 [details]
storage.log

Comment 7 Petr Janda 2019-11-06 16:47:00 UTC
Created attachment 1633383 [details]
storage.state

Comment 8 Petr Janda 2019-11-06 16:47:04 UTC
Created attachment 1633384 [details]
syslog

Comment 11 RHEL Program Management 2021-05-06 07:30:26 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.


Note You need to log in before you can comment on or make changes to this bug.