| Summary: | DispatchError: Can not reschedule step 'bootloader' from 'skipped' to 'requested' | ||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | He Rui <rhe> | ||||||||||
| Component: | anaconda | Assignee: | Ales Kozumplik <akozumpl> | ||||||||||
| Status: | CLOSED ERRATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||||||||
| Severity: | medium | Docs Contact: | |||||||||||
| Priority: | medium | ||||||||||||
| Version: | 19 | CC: | anaconda-maint-list, awilliam, jonathan, jzeleny, rhe, tflink, vanmeeuwen+fedora | ||||||||||
| Target Milestone: | --- | ||||||||||||
| Target Release: | --- | ||||||||||||
| Hardware: | x86_64 | ||||||||||||
| OS: | Linux | ||||||||||||
| Whiteboard: | anaconda_trace_hash:d618be89e3361ead2d0fc4563ccbd7efe2b95dd7b2dfba9019e59f76d706e723 | ||||||||||||
| Fixed In Version: | anaconda-16.15-1 | Doc Type: | Bug Fix | ||||||||||
| Doc Text: | Story Points: | --- | |||||||||||
| Clone Of: | Environment: | ||||||||||||
| Last Closed: | 2013-05-12 23:09:27 UTC | Type: | --- | ||||||||||
| Regression: | --- | Mount Type: | --- | ||||||||||
| Documentation: | --- | CRM: | |||||||||||
| Verified Versions: | Category: | --- | |||||||||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||||||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||||||||
| Attachments: |
|
||||||||||||
Created attachment 514156 [details]
Attached traceback automatically from anaconda.
Created attachment 514157 [details]
Attached traceback automatically from anaconda.
steps: 1. Installed a rawhide system using: http://serverbeach1.fedoraproject.org/pub/alt/stage/20110714/x86_64/iso/, make sure that bios boot partition existed. 2. Boot the same anaconda onto the installed system, exception occurred when examining storage devices. Created attachment 515426 [details]
Attached traceback automatically from anaconda.
(In reply to comment #3) > steps: > 1. Installed a rawhide system using: > http://serverbeach1.fedoraproject.org/pub/alt/stage/20110714/x86_64/iso/, make > sure that bios boot partition existed. > 2. Boot the same anaconda onto the installed system, exception occurred when > examining storage devices. Correction. This issue was triggered by kickstart install, in which partitioning part is not specified. So when anaconda prompted for user interaction at partition step, clicked next, exception would occur after 'detecting storage devices'. kickstart is like: install graphical cdrom lang en_US.UTF-8 keyboard us authconfig --enableshadow --enablemd5 timezone America/New_York --netmask=255.255.255.0 -\ rootpw `````` firewall --disabled selinux --disabled bootloader --location mbr reboot %packages %end Reporter, can you please retest with updates=http://akozumpl.fedorapeople.org/bz723798.img on the kernel command line? Thank you. Ales (In reply to comment #6) > Reporter, > > can you please retest with > updates=http://akozumpl.fedorapeople.org/bz723798.img on the kernel command > line? > > Thank you. > Ales Cool, it resolves the issue. Thanks. Fix pushed, 8387584c5bfebb76ad68f86f51c643c74b8d1efd. (In reply to comment #6) > Reporter, > > can you please retest with > updates=http://akozumpl.fedorapeople.org/bz723798.img on the kernel command > line? > > Thank you. > Ales Wow, I've done more tests on it. By using this updates with the same semi-kickstart environment as before, when checking: 1. 'replace existing linux partitons' + 'review and modify partition layout': PASS 2. 'Create custom layout' + 'review and modify partition layout': FAIL So the updates half solves the problems. Change it back to ASSIGNED. Sorry about that. *** Bug 727758 has been marked as a duplicate of this bug. ***
> Wow, I've done more tests on it. By using this updates with the same
> semi-kickstart environment as before, when checking:
>
> 1. 'replace existing linux partitons' + 'review and modify partition layout':
> PASS
>
> 2. 'Create custom layout' + 'review and modify partition layout': FAIL
>
> So the updates half solves the problems. Change it back to ASSIGNED. Sorry
> about that.
Can you please attach the new traceback?
Thanks.
(In reply to comment #12) > > Wow, I've done more tests on it. By using this updates with the same > > semi-kickstart environment as before, when checking: > > > > 1. 'replace existing linux partitons' + 'review and modify partition layout': > > PASS > > > > 2. 'Create custom layout' + 'review and modify partition layout': FAIL > > > > So the updates half solves the problems. Change it back to ASSIGNED. Sorry > > about that. > > Can you please attach the new traceback? > > Thanks. please refer to comment#11 (In reply to comment #13) > (In reply to comment #12) > > > Wow, I've done more tests on it. By using this updates with the same > > > semi-kickstart environment as before, when checking: > > > > > > 1. 'replace existing linux partitons' + 'review and modify partition layout': > > > PASS > > > > > > 2. 'Create custom layout' + 'review and modify partition layout': FAIL > > > > > > So the updates half solves the problems. Change it back to ASSIGNED. Sorry > > > about that. > > > > Can you please attach the new traceback? > > > > Thanks. > > please refer to comment#11 Please attach what I ask for. If you use the updates image the traceback is different although you think they might be the same. Also please attach /tmp/*log.
> > please refer to comment#11
>
> Please attach what I ask for. If you use the updates image the traceback is
> different although you think they might be the same. Also please attach
> /tmp/*log.
Sorry now I see what you meant. The new traceback is the new bug you closed as a duplicate.
Created attachment 516452 [details]
/tmp/* files
(In reply to comment #15) > > > please refer to comment#11 > > > > Please attach what I ask for. If you use the updates image the traceback is > > different although you think they might be the same. Also please attach > > /tmp/*log. > > Sorry now I see what you meant. The new traceback is the new bug you closed as > a duplicate. For traceback, please refer to: https://bugzilla.redhat.com/show_bug.cgi?id=727758#c3 (In reply to comment #15) > > > please refer to comment#11 > > > > Please attach what I ask for. If you use the updates image the traceback is > > different although you think they might be the same. Also please attach > > /tmp/*log. > > Sorry now I see what you meant. The new traceback is the new bug you closed as > a duplicate. That's correct, I've also attached a new one. It seems there is going to be a couple more places where we shouldn't force requesting a particular step. He Rui, can you please retest with http://akozumpl.fedorapeople.org/bz723798_2.img ? Thank you. (In reply to comment #19) > It seems there is going to be a couple more places where we shouldn't force > requesting a particular step. > > He Rui, can you please retest with > http://akozumpl.fedorapeople.org/bz723798_2.img ? > > Thank you. No luck, the result is the same as the previous updates image. see: https://bugzilla.redhat.com/show_bug.cgi?id=727758#c4 Hm, can you please retest with: http://akozumpl.fedorapeople.org/bz_dispatcher.img And attach the traceback you are getting? Thanks. (In reply to comment #21) > Hm, can you please retest with: > http://akozumpl.fedorapeople.org/bz_dispatcher.img > > And attach the traceback you are getting? > > Thanks. I can't attach any traceback as it seems fix the issue.:) Thanks. Fixed by c3bedc8c5b1542e882824d5fb4005f6336e7822a. For F16 this will be a part of the first post-alpha Anaconda build. *** Bug 730446 has been marked as a duplicate of this bug. *** This bug appears to have been reported against 'rawhide' during the Fedora 19 development cycle. Changing version to '19'. (As we did not run this process for some time, it could affect also pre-Fedora 19 development cycle bugs. We are very sorry. It will help us with cleanup during Fedora 19 End Of Life. Thank you.) More information and reason for this action is here: https://fedoraproject.org/wiki/BugZappers/HouseKeeping/Fedora19 This was clearly fixed long ago, closing. |
The following was filed automatically by anaconda: anaconda 16.12 exception report Traceback (most recent call first): File "/usr/lib64/python2.7/site-packages/pyanaconda/dispatch.py", line 98, in _reschedule self.namesched(to_sched))) File "/usr/lib64/python2.7/site-packages/pyanaconda/dispatch.py", line 118, in request return self._reschedule(self.SCHED_REQUESTED, current_step) File "/usr/lib64/python2.7/site-packages/pyanaconda/dispatch.py", line 291, in <lambda> changes = map(lambda s: self.steps[s].request(self._current_step()), steps) File "/usr/lib64/python2.7/site-packages/pyanaconda/dispatch.py", line 291, in request_steps changes = map(lambda s: self.steps[s].request(self._current_step()), steps) File "/usr/lib64/python2.7/site-packages/pyanaconda/iw/autopart_type.py", line 205, in getNext self.dispatch.request_steps("bootloader") File "/usr/lib64/python2.7/site-packages/pyanaconda/gui.py", line 1196, in nextClicked rc = self.currentWindow.getNext () DispatchError: Can not reschedule step 'bootloader' from 'skipped' to 'requested'