Created attachment 515282 [details] proposed patch Description of problem: cmdline mode kickstart install failure Version-Release number of selected component (if applicable): * anaconda-16.13 Steps to Reproduce: 1. https://fedoraproject.org/wiki/QA:Testcase_Anaconda_User_Interface_Cmdline Actual results: Running anaconda 16.13, the Fedora system installer - please wait. Traceback (most recent call last): File "/usr/sbin/anaconda", line 747, in <module> setupDisplay(anaconda, opts) File "/usr/sbin/anaconda", line 537, in setupDisplay anaconda.initInterface() File "/tmp/updates/pyanaconda/__init__.py", line 255, in initInterface from cmdline import InstallInterface File "/tmp/updates/pyanaconda/cmdline.py", line 37, in <module> stepToClasses = { "install" : setupProgressDisplay } NameError: name 'setupProgressDisplay' is not defined Expected results: No traceback Additional info: * This impacts the F16 Beta release criteria regarding installation automation - "Any installation method or process designed to run unattended must do so (there should be no prompts requiring user intervention) "
Seems related to commit 8b6d7f89
Ales has patch for it.
Hi James, Can you please retest with http://akozumpl.fedorapeople.org/bz725757.img ? The patch is here: https://www.redhat.com/archives/anaconda-devel-list/2011-July/msg00153.html Thank you. Ales
(In reply to comment #3) > Hi James, > > Can you please retest with http://akozumpl.fedorapeople.org/bz725757.img ? Resolves the reported problem, thanks!
Thanks for testing, pushed as 6caf7e595148a329b4cce915f9d872e196447f9e.
*** Bug 727810 has been marked as a duplicate of this bug. ***
It seems still happen in F16-alpha-RC1.
(In reply to comment #7) > It seems still happen in F16-alpha-RC1. Can you please attach the complete traceback? Thanks.
Created attachment 517354 [details] error log of anaconda 16.14.3
(In reply to comment #8) > (In reply to comment #7) > > It seems still happen in F16-alpha-RC1. > > Can you please attach the complete traceback? Thanks. Hi Ales, I have just test F16-alpha-RC2(anaconda 16.14.3), and still meet this error. The attachment is the screen shot of the error on F16-alpha-RC2. Pleas have a look, thanks.
Hi, it looks like my change hasn't been merged to the f16-alpha-branch. Can you please retest with post-alpha Anaconda? Ales
(In reply to comment #11) > Hi, > > it looks like my change hasn't been merged to the f16-alpha-branch. Can you > please retest with post-alpha Anaconda? > > Ales Okay, I will test with post-alpha Anaconda, thanks!
Hi Ales, It seems still happen in F16-alpha-RC4, i386 dvd install. The screen shot and anaconda log are in the attachment.
Created attachment 518429 [details] screen shot of error message
Created attachment 518432 [details] error log of anaconda 16.14.5
tao: it's expected to happen in all Alpha builds. this bug is not Alpha critical, so the fix is not in any Alpha builds. you'd need to build a test ISO with an anaconda build 16.15 or later - not a build on the 16.14 branch - to check this. 16.14 is the branch for Alpha. -- Fedora Bugzappers volunteer triage team https://fedoraproject.org/wiki/BugZappers
Discussed in the 2011-08-26 blocker review meeting. Accepted as a Fedora 16 beta blocker as it violates the following beta release criterion [1]: Any installation method or process designed to run unattended must do so (there should be no prompts requiring user intervention) [1] https://fedoraproject.org/wiki/Fedora_16_Beta_Release_Criteria
Tao and/or James: can you please confirm that this is fixed in Beta TC1? Thanks!
I was able to complete an unattended, cmdline kickstart-based minimal install of Beta TC2 using the ks http://www.happyassassin.net/extras/ordered_unattended.ks . BobLFoot also reported a 'pass' for this test case in the matrix. So I'm closing this as ERRATA (the fixed anaconda was already pushed to stable).