Description of problem: While testing bug#248447, it was discovered that you can trigger a traceback when adding a zFCP device with no details. It looks like anaconda is trying to pop-up a dialog noting no details were provided ... but it tracebacks due to incorrect args to a gtk function Version-Release number of selected component (if applicable): RHEL-5-Server/U1 - anaconda-11.1.2.87-1 How reproducible: 100% Steps to Reproduce: At the Disk prompt, 1) Add another storage device 2) Select zFCP 3) Click Add (without entering disk details). Actual results: traceback Expected results: Dialog noting incorrect user-entered data Additional info:
Created attachment 291196 [details] traceback.txt
diff --git a/iw/autopart_type.py b/iw/autopart_type.py index 47d57f1..59f8eea 100644 --- a/iw/autopart_type.py +++ b/iw/autopart_type.py @@ -190,7 +190,7 @@ class PartitionTypeWindow(InstallWindow): try: self.anaconda.id.zfcp.addFCP(devnum, wwpn, fcplun) except ValueError, e: - self.intf.messageWindow(_("Error"), e) + self.intf.messageWindow(_("Error"), "%s" % e) continue break
An advisory has been issued which should help the problem described in this bug report. This report is therefore being closed with a resolution of ERRATA. For more information on the solution and/or where to find the updated files, please follow the link below. You may reopen this bug report if the solution does not work for you. http://rhn.redhat.com/errata/RHBA-2008-0397.html
*** Bug 427839 has been marked as a duplicate of this bug. ***