The following was filed automatically by anaconda: anaconda 11.5.0.47 exception report Traceback (most recent call first): File "/usr/lib/anaconda/iutil.py", line 106, in execWithRedirect except OSError, (errno, msg): File "/usr/lib/anaconda/storage/udev.py", line 169, in udev_trigger iutil.execWithRedirect("udevadm", argv, stderr="/dev/null", searchPath=1) File "/usr/lib/anaconda/storage/__init__.py", line 65, in storageInitialize udev_trigger(subsystem="block") File "/usr/lib/anaconda/dispatch.py", line 205, in moveStep rc = stepFunc(self.anaconda) File "/usr/lib/anaconda/dispatch.py", line 128, in gotoNext self.moveStep() File "/usr/lib/anaconda/gui.py", line 1330, in nextClicked self.anaconda.dispatch.gotoNext() ValueError: need more than 0 values to unpack
Created attachment 340958 [details] Attached traceback automatically from anaconda.
Can you reliably reproduce this?
"need more than 0 values to unpack"? That's strange, isn't it? I'd assume it would be one value - the exception instance. But maybe my understanding of exception handling is incomplete. Anyway, here's a suggested patch for execWithRedirect: diff --git a/iutil.py b/iutil.py index 0d7faed..7d354b7 100644 --- a/iutil.py +++ b/iutil.py @@ -103,8 +103,8 @@ def execWithRedirect(command, argv, stdin = None, stdout = None, if proc.returncode is not None: ret = proc.returncode break - except OSError, (errno, msg): - errstr = "Error running %s: %s" % (command, msg) + except OSError, e: + errstr = "Error running %s: %s" % (command, e.strerror) log.error(errstr) runningLog.write(errstr) runningLog.close() Haven't tried to reproduce yet - restarting the install now.
Hrm. Can't reproduce so far. Might be some kind of unreliable race with udevadm or something? Or maybe I just got a bad image? Who knows. I'll keep trying.
Well, I've pushed your patch above for all places where we catch OSError. I did the same thing in rhpl a little while back and haven't seen any new complaints. Hopefully this will take care of it.