Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.
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 597199

Summary: RuntimeError: Error running multipath: No such file or directory
Product: Red Hat Enterprise Linux 6 Reporter: Marian Ganisin <mganisin>
Component: distributionAssignee: RHEL Program Management <pm-rhel>
Status: CLOSED WONTFIX QA Contact: Ben Levenson <benl>
Severity: medium Docs Contact:
Priority: medium    
Version: 6.0CC: akozumpl, mbanas, notting, syeghiay
Target Milestone: rcKeywords: Reopened
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard: anaconda_trace_hash:4eefec4a8be4d590afb6616b73575870e40d9de16eb69dc59874360a5ee4a16e
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2010-06-03 21:11:05 UTC Type: ---
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: 582286, 590407    
Attachments:
Description Flags
Attached traceback automatically from anaconda.
none
Attached traceback automatically from anaconda.
none
Attached traceback automatically from anaconda.
none
Attached traceback automatically from anaconda. none

Description Marian Ganisin 2010-05-28 11:21:09 UTC
The following was filed automatically by anaconda:
anaconda 13.21.48 exception report
Traceback (most recent call first):
  File "/usr/lib/anaconda/iutil.py", line 236, in execWithCapture
    raise RuntimeError, "Error running " + command + ": " + e.strerror
  File "/usr/lib/anaconda/storage/devicelibs/mpath.py", line 80, in identifyMultipaths
    topology = parseMultipathOutput(iutil.execWithCapture("multipath", ["-d",]))
  File "/usr/lib/anaconda/iw/filter_gui.py", line 570, in getScreen
    (singlepaths, mpaths, partitions) = identifyMultipaths(disks)
  File "/usr/lib/anaconda/gui.py", line 1415, in setScreen
    new_screen = self.currentWindow.getScreen(anaconda)
  File "/usr/lib/anaconda/gui.py", line 1336, in nextClicked
    self.setScreen ()
RuntimeError: Error running multipath: No such file or directory

Comment 1 Marian Ganisin 2010-05-28 11:21:19 UTC
Created attachment 417570 [details]
Attached traceback automatically from anaconda.

Comment 3 Martin Banas 2010-05-28 11:47:11 UTC
Created attachment 417585 [details]
Attached traceback automatically from anaconda.

Comment 4 Martin Banas 2010-05-28 11:48:31 UTC
Same on x86_64, changing the architecture to all.

Comment 5 Chris Lumens 2010-05-28 14:17:32 UTC
Isn't this another instance of the case where the Client variant does not include the multipath tools?

Comment 6 Bill Nottingham 2010-05-28 21:00:28 UTC
Yes. Does this happen during the non-Live installation path?

Comment 7 Marian Ganisin 2010-06-01 05:13:41 UTC
(In reply to comment #6)
> Yes. Does this happen during the non-Live installation path?    

No, it doesn't.

Comment 8 Bill Nottingham 2010-06-01 19:36:53 UTC
Live installation isn't a supported path, ergo, closing.

Comment 9 Marian Ganisin 2010-06-02 12:06:08 UTC
Sorry for opening this again, however few questions need answers.

Resolution seems to be in conflict with Bug 222198, doesn't it?

If it is not supported, do we want to provide Live CD?

If yes, do we want to provide Live CD with installation icon on desktop?

Comment 10 Bill Nottingham 2010-06-02 15:14:48 UTC
Those are questions for PM. As I understand the current situation:

- LiveCDs are built as a testing tool
- Installation is not supported from them
- We're not planning on shipping the live images to partners/customers

Ergo, while we may want to nuke the installation icon, it's not a huge deal.

Comment 12 Ales Kozumplik 2010-06-09 07:23:54 UTC
Created attachment 422455 [details]
Attached traceback automatically from anaconda.

Comment 13 Ales Kozumplik 2010-06-09 07:25:26 UTC
Created attachment 422456 [details]
Attached traceback automatically from anaconda.