Bug 676025
| Summary: | anaconda crashes in text mode on creating boot loader | ||||||
|---|---|---|---|---|---|---|---|
| Product: | Red Hat Enterprise Linux 6 | Reporter: | Martin Jürgens <ma> | ||||
| Component: | anaconda | Assignee: | Brian Lane <bcl> | ||||
| Status: | CLOSED ERRATA | QA Contact: | Release Test Team <release-test-team-automation> | ||||
| Severity: | medium | Docs Contact: | |||||
| Priority: | unspecified | ||||||
| Version: | 6.0 | CC: | atodorov, charlieb-fedora-bugzilla, pholica, rwilliam | ||||
| Target Milestone: | rc | Flags: | pholica:
needinfo-
|
||||
| Target Release: | --- | ||||||
| Hardware: | x86_64 | ||||||
| OS: | Linux | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | anaconda-13.21.123-1 | Doc Type: | Bug Fix | ||||
| Doc Text: |
Users performing an upgrade using the Anaconda's text mode interface who do not have a boot loader already installed on the system, or who have a non-GRUB boot loader, need to select Skip Boot Loader Configuration during the installation process. Boot loader configuration will need to be completed manually after installation. This problem does not affect users running Anaconda in the graphical mode (graphical mode also includes VNC connectivity mode).
|
Story Points: | --- | ||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2011-12-06 10:29:54 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: | |||||||
| Attachments: |
|
||||||
This is fixed by 63fb1731cd77976f99b42dbf2c3598821b7faaff from master, which may or may not apply too well to rhel6-branch. *** Bug 688351 has been marked as a duplicate of this bug. *** This request was evaluated by Red Hat Product Management for inclusion in a Red Hat Enterprise Linux maintenance release. Product Management has requested further review of this request by Red Hat Engineering, for potential inclusion in a Red Hat Enterprise Linux Update release for currently deployed products. This request is not yet committed for inclusion in an Update release. (In reply to comment #2) > This is fixed by 63fb1731cd77976f99b42dbf2c3598821b7faaff from master, which > may or may not apply too well to rhel6-branch. That should be a question which is easy to resolve. Does it or does it not apply? The answer is "yes" - it does apply: bash-3.2$ lynx -dump 'http://git.fedorahosted.org/git?p=anaconda.git;a=blobdiff_plain;f=textw/upgrade_bootloader_text.py;h=1512b1dfdb245b41b1c09c98282f75370c6b917f;hp=db736f35c709c97cbeb4a7b4720932387031b7f7;hb=63fb1731cd77976f99b42dbf2c3598821b7faaff;hpb=fce670e62c43ff293718e63601e247de1b7dd3ea' | patch -p1 patching file textw/upgrade_bootloader_text.py bash-3.2$ pwd /tmp/anaconda-13.21.82 bash-3.2$ Please fix this for RHEL 6.2. (In reply to comment #0) > Steps to Reproduce: > 1. start anaconda in text mode using upgradeany with a different bootloader > installed in mbr Martin, what boot loader did you use? Hello, this fix introduced new bug 754375. There should be at least release note saying, that manual text upgrade without installed bootloader (or with different bootloader) (which is very limited scenario) doesn't have default option and one needs to select "Skip boot loader configuration".
Technical note added. If any revisions are required, please edit the "Technical Notes" field
accordingly. All revisions will be proofread by the Engineering Content Services team.
New Contents:
Users performing an upgrade using the text mode interface who do not have a boot loader already installed on the system or who have a non-grub boot loader will need to select "Skip Boot Loader Configuration" during installation. Boot loader configuration will need to be completed manually after installation. This problem does not affect users running anaconda in graphical mode (graphical mode also includes VNC connectivity mode).
Technical note updated. If any revisions are required, please edit the "Technical Notes" field
accordingly. All revisions will be proofread by the Engineering Content Services team.
Diffed Contents:
@@ -1 +1 @@
-Users performing an upgrade using the text mode interface who do not have a boot loader already installed on the system or who have a non-grub boot loader will need to select "Skip Boot Loader Configuration" during installation. Boot loader configuration will need to be completed manually after installation. This problem does not affect users running anaconda in graphical mode (graphical mode also includes VNC connectivity mode).+Users performing an upgrade using the Anaconda's text mode interface who do not have a boot loader already installed on the system, or who have a non-GRUB boot loader, need to select Skip Boot Loader Configuration during the installation process. Boot loader configuration will need to be completed manually after installation. This problem does not affect users running Anaconda in the graphical mode (graphical mode also includes VNC connectivity mode).
Thanks for technical note. It fully describes situation, so I'm moving this bug to verified. Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. http://rhn.redhat.com/errata/RHBA-2011-1565.html |
Created attachment 477642 [details] anaconda traceback Description of problem: anaconda crashes in text mode on creating boot loader Version-Release number of selected component (if applicable): How reproducible: Always Steps to Reproduce: 1. start anaconda in text mode using upgradeany with a different bootloader installed in mbr 2. anaconda offers to replace it Actual results: crash, see trackback Expected results: should work fine as it does in graphical mode. Additional info: