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.
Previously, Red Hat Enterprise Virtualization did not have a boot menu option that provided a clean install. In some cases, attempting a clean install could lead to NIC devices being improperly configured.
Red Hat Enterprise Virtualization now has a boot menu option which provides a clean install which properly configures NIC devices.
As per IRC/rhev-devel discussion we've been seeing issues in the field with beta and need to provide a simple option for a clean installation.
Long term solution is to handle this within the installer but that's out of scope now for 6.2 so short term is to add a grub option to wipe the existing HostVG before running the installer.
Attachment shows proposed changes.
Comment so far:
Update "Boot" to "Install or Upgrade"
ditto for "with serial console"
Add reinstall with serial console
Created attachment 519904[details]
Version 2
Incorporate updates from previous comment
Note: second Reinstall entry will be Reinstall with serial console
Details are shown for Reinstall with serial console
Created attachment 519948[details]
Patch
Patch to add reinstall and uninstall options to the boot menu. This provides a boot menu like the version 2 attachment with the "Reinstall with serial console" label fixed
I like Andrew's original comment about moving the 'Uninstall' option to within the ovirt-install TUI menu. That would make it so the user doesn't have to incur an additional reboot and it would be a more obvious option. I didn't realize the Uninstall option was even on the GRUB menu until afer I'd already gone through the trouble of 'dd'ing the drive.
It seems like it would be a more obvious option for the TUI menu since you could present the use with an auto-detected storage device to Uninstall from, it would preform the operation, and then dump the user back to an Install prompt all without reboot.
What is the use case for uninstall?
The case you described can be handled by using the "Reinstall" option in the Boot Menu. If you want to install a new version, then you need to boot from media anyway.
Reinstall doesn't seem to remove everything. For example, I chose reinstall and it still had my NIC devices configured how I had them before. Perhaps that was a beta 2 bug that is now fixed in beta 3; I haven't tried it yet.
Where does this BZ stand as of 6 Dec 2011?
Is it possible to do a clean install from the boot menu?
If you're interested, you should know that BZ#747102 is related to this bug. Upgrading from beta to GA RHEV causes the host to be incorrectly partitioned.
Is this fixed in Beta 3? In order to be fixed in Beta 3, I reckon 1) the boot menu should include an option for a clean install, and 2) NIC devices should not be configured the way they were before the clean install (see Bryan Yount's Comment 11).
Cheers!
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-1783.html
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:
Previously, Red Hat Enterprise Virtualization did not have a boot menu option that provided a clean install. In some cases, attempting a clean install could lead to NIC devices being improperly configured.
Red Hat Enterprise Virtualization now has a boot menu option which provides a clean install which properly configures NIC devices.