Bug 572853 - TypeError: execWithRedirect() got an unexpected keyword argument 'searchPath'
Summary: TypeError: execWithRedirect() got an unexpected keyword argument 'searchPath'
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: anaconda
Version: 14
Hardware: i386
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Hans de Goede
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: anaconda_trace_hash:caa00f141e0e434a9...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-03-12 07:53 UTC by He Rui
Modified: 2012-08-16 22:37 UTC (History)
2 users (show)

Fixed In Version: anaconda-13.34-1
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-08-16 22:37:55 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
Attached traceback automatically from anaconda. (323.04 KB, text/plain)
2010-03-12 07:53 UTC, He Rui
no flags Details

Description He Rui 2010-03-12 07:53:18 UTC
The following was filed automatically by anaconda:
anaconda 13.32 exception report
Traceback (most recent call first):
  File "/usr/lib/anaconda/storage/fcoe.py", line 115, in addSan
    searchPath = 1)
  File "/usr/lib/anaconda/iw/advanced_storage.py", line 98, in addFcoeDrive
    intf=anaconda.intf)
  File "/usr/lib/anaconda/iw/advanced_storage.py", line 247, in addDrive
    rc = addFcoeDrive(anaconda)
  File "/usr/lib/anaconda/iw/filter_gui.py", line 416, in _add_advanced_clicked
    if not addDrive(self.anaconda):
TypeError: execWithRedirect() got an unexpected keyword argument 'searchPath'

Comment 1 He Rui 2010-03-12 07:53:24 UTC
Created attachment 399576 [details]
Attached traceback automatically from anaconda.

Comment 2 He Rui 2010-03-12 08:07:21 UTC
Description of problem:
I virt-installed anaconda 13.32 of f13-alpha-rc4 and exception occurred while adding FCoE SAN advanced storage in Specialized storage devices.  

How reproducible:
100%

Version:
anaconda13.32

Steps to Reproduce:
1. Start installing f13-alpha-rc4 DVD.iso in kvm
2. Choose Specialized storage devices and proceed
3. Click Add Adavanced Target and select Add FCoE SAN to Add Drive
4. Exception occurred

Comment 3 Hans de Goede 2010-03-12 08:21:34 UTC
Thanks for the bug report! I've a patch fixing this, but since we're post F-13 alpha we are taking blocker fixes only, I'll try to get an exception for this.

p.s.

Do you have access to actual FCoE hardware to test ? If so that would be great FcoE is very much completely untested atm.

Comment 4 He Rui 2010-03-12 09:52:11 UTC
(In reply to comment #3)
> Do you have access to actual FCoE hardware to test ? If so that would be great
> FcoE is very much completely untested atm.    

Sorry, I'm afraid not. This exception was occurred when I had no connection to FCoE HW.

Comment 5 Hans de Goede 2010-03-15 13:10:08 UTC
The fix for the reported backtrace will be in anaconda-13.34-1, changing the status to modified.

Comment 6 Fedora Update System 2010-03-23 21:29:53 UTC
anaconda-13.36-1.fc13 has been submitted as an update for Fedora 13.
http://admin.fedoraproject.org/updates/anaconda-13.36-1.fc13

Comment 7 Fedora Update System 2010-03-24 00:48:10 UTC
anaconda-13.36-1.fc13 has been pushed to the Fedora 13 testing repository.  If problems still persist, please make note of it in this bug report.
 If you want to test the update, you can install it with 
 su -c 'yum --enablerepo=updates-testing update anaconda'.  You can provide feedback for this update here: http://admin.fedoraproject.org/updates/anaconda-13.36-1.fc13

Comment 8 He Rui 2010-03-24 05:54:48 UTC
This issue still happens in anaconda 13.36-1 if the network didn't start in advance.

Comment 9 Bug Zapper 2010-07-30 11:02:55 UTC
This bug appears to have been reported against 'rawhide' during the Fedora 14 development cycle.
Changing version to '14'.

More information and reason for this action is here:
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Comment 10 Fedora End Of Life 2012-08-16 22:37:58 UTC
This message is a notice that Fedora 14 is now at end of life. Fedora 
has stopped maintaining and issuing updates for Fedora 14. It is 
Fedora's policy to close all bug reports from releases that are no 
longer maintained.  At this time, all open bugs with a Fedora 'version'
of '14' have been closed as WONTFIX.

(Please note: Our normal process is to give advanced warning of this 
occurring, but we forgot to do that. A thousand apologies.)

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, feel free to reopen 
this bug and simply change the 'version' to a later Fedora version.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we were unable to fix it before Fedora 14 reached end of life. If you 
would still like to see this bug fixed and are able to reproduce it 
against a later version of Fedora, you are encouraged to click on 
"Clone This Bug" (top right of this page) and open it against that 
version of Fedora.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events.  Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

The process we are following is described here: 
http://fedoraproject.org/wiki/BugZappers/HouseKeeping


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