Bug 750809
| Summary: | Anaconda doesn't reboot when installation is prematurely exited | ||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Kamil Páral <kparal> | ||||||||||||||
| Component: | anaconda | Assignee: | Anaconda Maintenance Team <anaconda-maint-list> | ||||||||||||||
| Status: | CLOSED RAWHIDE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||||||||||||
| Severity: | unspecified | Docs Contact: | |||||||||||||||
| Priority: | unspecified | ||||||||||||||||
| Version: | 16 | CC: | anaconda-maint-list, awilliam, jonathan, tflink, vanmeeuwen+fedora | ||||||||||||||
| Target Milestone: | --- | ||||||||||||||||
| Target Release: | --- | ||||||||||||||||
| Hardware: | Unspecified | ||||||||||||||||
| OS: | Unspecified | ||||||||||||||||
| Whiteboard: | |||||||||||||||||
| Fixed In Version: | anaconda-17.2-1 | Doc Type: | Bug Fix | ||||||||||||||
| Doc Text: | Story Points: | --- | |||||||||||||||
| Clone Of: | Environment: | ||||||||||||||||
| Last Closed: | 2011-11-03 20:10:52 UTC | Type: | --- | ||||||||||||||
| Regression: | --- | Mount Type: | --- | ||||||||||||||
| Documentation: | --- | CRM: | |||||||||||||||
| Verified Versions: | Category: | --- | |||||||||||||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||||||||||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||||||||||||
| Embargoed: | |||||||||||||||||
| Bug Depends On: | |||||||||||||||||
| Bug Blocks: | 713566 | ||||||||||||||||
| Attachments: |
|
||||||||||||||||
Created attachment 531337 [details]
anaconda.log
Created attachment 531338 [details]
program.log
Created attachment 531339 [details]
storage.log
Created attachment 531340 [details]
syslog
Created attachment 531341 [details]
X.log
Adam and Tim, do we care? (In reply to comment #6) > Adam and Tim, do we care? Well, it's a bug. Of course we care but as far as blockery-ness goes? I'm thinking probably not. The workaround is pretty easy and it's a minor glitch in a failure mode. I don't think that having to manually reboot after exiting anaconda is a huge deal. Not enough to re-spin anaconda post-freeze if we got a fix, anyways. I'm -1 NTH on this. |
Created attachment 531336 [details] final screen when waiting for reboot Description of problem: When anaconda is exited prematurely, from whatever reason, by clicking the button "Exit installer" in the popup dialog, the computer is not rebooted. The initial anaconda's blue screen (haha) is shown, nothing else. I have waited more than 5 minutes, it just sits still. Computer can be restarted manually by hitting Ctrl+Alt+Delete (if you know this combination of course). The shell on tty2 also works. Version-Release number of selected component (if applicable): Fedora 16 RC4 anaconda 16.24 How reproducible: always Steps to Reproduce: 1. Confirm all defaults up to the partitioning step 2. Do the partitioning, write the changes to the disk 3. Hit Back on the next form, confirm Exit installer 4. Wait for reboot 5. Wait for reboot... 6. Wait for reboot..... Actual results: no reboot Expected results: reboot