Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
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).
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:
*** Bug 688351 has been marked as a duplicate of this bug. ***
Comment 4RHEL Program Management
2011-05-13 23:08:00 UTC
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?
Comment 9Alexander Todorov
2011-08-09 10:00:38 UTC
(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).
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: