Description of problem: upgrade failed from f15 to f16, Dispatch error:cannot reschedule step 'findinstall' from 'skipped' to 'requested' Version-Release number of selected component (if applicable): How reproducible: 100% Steps to Reproduce: 1. install previous release 2. upgrade f16 from DVD 3. Actual results: Expected results: Additional info:
Created attachment 516679 [details] anaconda.log
Created attachment 516680 [details] syslog
Created attachment 516681 [details] program log
Hi, can you please retest with: http://akozumpl.fedorapeople.org/bz_dispatcher.img And see if it fixes the problem or attach the new traceback? Thanks.
Proposing as a F16Beta release blocker due to the following criteria ... "The installer must be able to successfully complete an upgrade installation from a clean, fully updated default installation (from any official install medium) of the previous stable Fedora release, either via preupgrade or by booting to the installer manually. The upgraded system must meet all release criteria "
(In reply to comment #4) > Hi, can you please retest with: > http://akozumpl.fedorapeople.org/bz_dispatcher.img > > And see if it fixes the problem or attach the new traceback? > > Thanks. I have tested it, error still occured: cannot reschedule step 'cleardiskssel' from 'skipped' to 'requested'. logs can be found in the attachment log.tar
Created attachment 516971 [details] upgrade logs
*** Bug 728122 has been marked as a duplicate of this bug. ***
this is reproduced on f16-alpha-rc1
Hi, thanks for the testing, I made a new image updates image which is supposed to fix the error from comment 7: http://akozumpl.fedorapeople.org/bz_dispatcher2.img Can you please try it?
Hi, Ales, The "'NoneType' object is not subscriptable" error occured, please find the details from the attachments.
Created attachment 517123 [details] upgrade log with updates image2
(In reply to comment #11) > Hi, Ales, > > The "'NoneType' object is not subscriptable" error occured, please find the > details from the attachments. I think you are hitting a new error, because the logs show you moved past the original point of failure. I am going to push my fix, once it gets into f16 builds (post alpha probably?) you can open the new bug.
Proposed patch: https://www.redhat.com/archives/anaconda-devel-list/2011-August/msg00080.html.
Fixed by c3bedc8c5b1542e882824d5fb4005f6336e7822a.
For F16 this will be a part of the first post-alpha Anaconda build.
With both Fedora 16 Alpha RC1 and RC3, I get a similar but different dispatch error. When I click the next button after selecting my Fedora 15 partition to upgrade, I get something like: Dispatch error:cannot reschedule step 'language' from 'skipped' to 'requested' I'm unable to save event though (doesn't like my wireless network and doesn't prompt for saving to disk) so this is from memory. The proposed patch in Comment 14 changes both 'findinstall' (title of this bug) and 'language' to both be schedule_steps_gently(). So its my hopes this will also fix my issue. I'll retest when updated ISO is available... but I wanted to get the phrase 'language' in comments for benefit of other users getting same variation of error. I'm unable to upgrade as-is.
(In reply to comment #17) > With both Fedora 16 Alpha RC1 and RC3, I get a similar but different dispatch > error. > > When I click the next button after selecting my Fedora 15 partition to upgrade, > I get something like: > > Dispatch error:cannot reschedule step 'language' from 'skipped' to 'requested' > > I'm unable to save event though (doesn't like my wireless network and doesn't > prompt for saving to disk) so this is from memory. > > The proposed patch in Comment 14 changes both 'findinstall' (title of this bug) > and 'language' to both be schedule_steps_gently(). So its my hopes this will > also fix my issue. > > I'll retest when updated ISO is available... but I wanted to get the phrase > 'language' in comments for benefit of other users getting same variation of > error. > > I'm unable to upgrade as-is. Your bug is the same with bug 728122
Thanks for pointer that bug 728112 is what I was seeing. I just tried RC4 with anaconda 16.14.5 and still see issue. I do not know if the comment 14 patch was ever committed. anaconda 16.14.5 exception report Traceback (most recent call first): File "/usr/lib/python2.7/site-packages/pyanaconda/dispatch.py", line 98, in _r eschedule self.namesched(to_sched))) File "/usr/lib/python2.7/site-packages/pyanaconda/dispatch.py", line 148, in s chedule return self._reschedule(self.SCHED_SCHEDULED, current_step) File "/usr/lib/python2.7/site-packages/pyanaconda/dispatch.py", line 308, in < lambda> changes = map(lambda s: self.steps[s].schedule(self._current_step()), steps) File "/usr/lib/python2.7/site-packages/pyanaconda/dispatch.py", line 308, in s chedule_steps changes = map(lambda s: self.steps[s].schedule(self._current_step()), steps) File "/usr/lib/python2.7/site-packages/pyanaconda/upgrade.py", line 288, in se tSteps "complete" File "/usr/lib/python2.7/site-packages/pyanaconda/iw/examine_gui.py", line 43, in getNext upgrade.setSteps(self.anaconda) File "/usr/lib/python2.7/site-packages/pyanaconda/gui.py", line 1194, in nextC licked rc = self.currentWindow.getNext () DispatchError: Can not reschedule step 'language' from 'skipped' to 'scheduled'
It was committed but it won't make Alpha. The problems with the dispatcher exist because I made a bunch of cleanups to it during f16 development and those are errors coming back. Since the upgrade path is not considered as critical for alpha we decided not to merge the latest fixes there and make the branch stable for the basic install sooner instead.
Adding keyword 'CommonBugs' to this issue so the problem can be documented until the bug is resolved in a post-Alpha anaconda build.
*** Bug 731255 has been marked as a duplicate of this bug. ***
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]: The installer must be able to successfully complete an upgrade installation from a clean, fully updated default installation (from any official install medium) of the previous stable Fedora release, either via preupgrade or by booting to the installer manually. The upgraded system must meet all release criteria [1] https://fedoraproject.org/wiki/Fedora_16_Beta_Release_Criteria
Hongqing, can you please confirm the status of this bug with Beta TC1? Thanks!
In my testing, this bug is fixed in TC2, and you run into https://bugzilla.redhat.com/show_bug.cgi?id=735730 later in install. Moving to VERIFIED for now, but it should probably be CLOSED. Hongqing, if you could confirm that would be great.