Created attachment 956098 [details] attached Screenshot for rhevh 7 welcome page.png Description of problem: At first clean install rhev-hypervisor6-6.6-20141107.0.iso, then boot from pxe server, select "rhev-hypervisor7-7.0-20141107.0" profile and add "reinstall" into this profile. But it still prompt "Major version upgrades are unsupported,uninstall existing version first" info when selecting "reinstall" option(seen rhevh 7 welcome page.png) Version-Release number of selected component (if applicable): rhev-hypervisor7-7.0-20141107.0 ovirt-node-3.1.0-0.25.20141107gitf6dc7b9.el7.noarch How reproducible: 100% Steps to Reproduce: 1. At first clean install rhev-hypervisor6-6.6-20141107.0.iso 2. then boot from pxe server, select "rhev-hypervisor7-7.0-20141107.0" profile and add "reinstall" into this profile. Actual results: After step2, it still prompt "Major version upgrades are unsupported,uninstall existing version first" info in welcome page when selecting "reinstall" option Expected results: it prompt "Install Hypervisor 7.0-20141107.0.el7ev" info in welcome page when selecting "reinstall" option Additional info:
Let's consider to fix it in rhev 3.5 beta phase.
reinstall does not work in rhevh 7.0 build. so urgent for this bug.
I was able to reproduce this bug with ISOs only: 1. Install latest 6.6 image 2. After reboot, use 7.0 image and boot with "reinstall" option 3. TUI installer prompts "Major version upgrades are unsupported"
the patch is merged yet on Nov 18, and the test build is rhev-hypervisor7-7.0-20141119.0
Test version: rhev-hypervisor7-7.0-20141212.0.iso ovirt-node-3.1.0-0.34.20141210git0c9c493.el7.noarch Test Steps: 1. At first clean install rhev-hypervisor6-6.6-20141107.0.iso 2. then boot from pxe server, select "rhev-hypervisor7-7.0-20141212.0.iso" profile and add "reinstall" into this profile. Test results: it prompt "Install Hypervisor 7.0-20141212.0.el7ev" info in welcome page when selecting "reinstall" option. So this bug has been fixed, changed 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. https://rhn.redhat.com/errata/RHEA-2015-0160.html