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, when an existing host volume group was detected on an installation device, users were prompted to overwrite the host volume group. Now, if a host volume group is detected on an installation device, users are prompted to reboot the hypervisor and select the reinstall option.
Description of problem:
Overwrite exited HostVG function didn't work during TUI install process
Version-Release number of selected component (if applicable):
rhev-hypervisor6-6.4-20121126.0.el6
How reproducible:
100%
Steps to Reproduce:
1. Boot from PXE and install RHEV-H.
2. Select USB device to use for booting RHEV-H.
3. Select USB device to use for installation of RHEV-H.
4. Finish the installation process.
5. Then unplug the usb media from local host
6. Boot from PXE and install RHEV-H via TUI.
7. Enter "Select the disk to use for booting RHEV Hyervisor" page
8. Plug that USB media(has been installed rhev-h) into local host.
9. Refresh the page and select USB device to use for booting RHEV-H.
10.Then enter "Please select the disk(s) to use for installation of RHEV Hyervisor" page.
11.Select USB media(has been installed rhev-h) to use for installation of RHEV-H.
12. Prompt that "Exiting HostVG Detected on /dev/sdb4, Overwrite?",then click "OK" button.
Actual result:
After step12, "Exiting HostVG Detected on /dev/sdb4, Overwrite?" function didn't work during install process
Expect result:
After step12, Overwrite exited HostVG Detected on /dev/sdb4 should success.
Test version:
rhev-hypervisor6-6.4-20121212.1.el6
ovirt-node-2.5.0-11.el6
Tested as follows:
Steps to Reproduce:
1. Boot from PXE and install RHEV-H.
2. Select USB device to use for booting RHEV-H.
3. Select USB device to use for installation of RHEV-H.
4. Finish the installation process.
5. Then unplug the usb media from local host
6. Boot from PXE and install RHEV-H via TUI.
7. Enter "Select the disk to use for booting RHEV Hyervisor" page
8. Plug that USB media(has been installed rhev-h) into local host.
9. Refresh the page and select USB device to use for booting RHEV-H.
10.Then enter "Please select the disk(s) to use for installation of RHEV Hyervisor" page.
11.Select USB media(has been installed rhev-h) to use for installation of RHEV-H.
Prompt that "Existing HostVG Detected on /dev/mapper/1SanDiskp4, Please reboot from media and choose Reinstall",then click "Reboot" button. rhev-h will reboot.
So this bug has been fixed, change the status into "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-2013-0556.html