The following was filed automatically by anaconda: anaconda 13.29 exception report Traceback (most recent call first): File "/usr/lib/anaconda/yuminstall.py", line 236, in callback ValueError: too many values to unpack
Created attachment 395934 [details] Attached traceback automatically from anaconda.
I don't know why this is reported as Fedora 12. This comes from trying to install the alpha rc2 of fedora 13.
I get the same thing when attempting to upgrade from a minimal F-12 system using F-13-Alpha-RC2. I also see a failure while attempting to present the error handling dialog. I've opened that against python-meh (see bug#567963) 13:10:35 Please manually connect your vnc client to test1247.test.redhat.com:1 (10.10.10.247) to begin the install. Press <enter> for a shell 13:10:36 Starting graphical installation. Error in sys.excepthook: Traceback (most recent call last): File "/usr/lib/python2.6/site-packages/meh/handler.py", line 162, in <lambda> File "/usr/lib/python2.6/site-packages/meh/handler.py", line 107, in handleException File "/usr/lib/anaconda/gui.py", line 1085, in mainExceptionWindow ImportError: No module named ui.gui Original exception was: Traceback (most recent call last): File "/usr/lib/anaconda/yuminstall.py", line 236, in callback ValueError: too many values to unpack error: python callback <bound method AnacondaCallback.callback of <yuminstall.AnacondaCallback instance at 0x7fde1da12518>> failed, aborting! /mnt/sysimage/var/lib/rpm: No such file or directory /mnt/sysimage/var/lib/rpm: No such file or directory install exited abnormally [1/1] The system will be rebooted when you press Ctrl-C or Ctrl-Alt-Delete.
Can someone attach the syslog to this bug report?
Created attachment 396093 [details] /tmp/*log.tgz -rw-r--r-- root/root 11475 2010-02-24 11:11 tmp/anaconda.log -rw-r--r-- root/root 3410 2010-02-24 11:12 tmp/minimon.log -rw-r--r-- root/root 18767 2010-02-24 11:08 tmp/program.log -rw-r--r-- root/root 61165 2010-02-24 11:12 tmp/storage.log -rw-r--r-- root/root 42578 2010-02-24 11:12 tmp/syslog -rwxr-xr-x root/root 880 2010-02-24 11:03 tmp/vncserver.log -rw-r--r-- root/root 2459 2010-02-24 11:08 tmp/yum.log
While upgrades are not listed in the F-13-Alpha release criteria (https://fedoraproject.org/wiki/Fedora_13_Alpha_Release_Criteria), I suspect many people will attempt upgrades. Adding keyword CommonBugs so adamw or I can document this issue for F-13-Alpha testers.
In my case, this was very serious and should be avoided by alpha testers who don't have a throw away configuration. Upon rebooting, I had a configuration which wouldn't run. It has a very bad mixture of f12 and f13 components, over 300 dupes including kernel-PAE, fedora-release, gcc and cpp. Package-cleanup wants to delete too much so this is going to have to be cleaned by hand. I would strongly advise people to avoid upgrading until this is fixed.
Looking at: http://git.fedorahosted.org/git/?p=anaconda.git;a=blob;f=yuminstall.py;hb=HEAD#l233 You see that this only occurs on a couple cases in the RPM callback - all errors. In testing, I hit this case a couple times during one upgrade. The first time during package installation, h was a tuple like we're expecting. The second time it happened is post-installation, I believe after rpm.RPM_CALLBACK_UNINST_START/STOP has been seen in the above case. This second time through, h is the string "cyrus-sasl". Any idea what's going on here? Shouldn't we be getting the same type as argument in all cases?
Chris, this is "normal" for rpm, we have a bunch of code in yum to handle it now Eg.: http://yum.baseurl.org/gitweb?p=yum.git;a=commitdiff;h=cf5765f74a23229abcc26b4e4cf5563b4d2cfeb6
Sigh, okay. Thanks for the pointer.
anaconda-13.32-1.fc13 has been submitted as an update for Fedora 13. http://admin.fedoraproject.org/updates/anaconda-13.32-1.fc13
anaconda-13.32-1.fc13 has been pushed to the Fedora 13 stable repository. If problems still persist, please make note of it in this bug report.
Removing CommonBugs keyword as this is already fixed in F-13-Alpha-RC4 (anaconda-13.32-1.fc13)