CURRENT IMPLEMENTATION ovirt-node can be either added like regular host or registered/approved. Once added, it can only be upgraded. NEW IMPLEMENTATION Support two options: 1. ovirt-node upgrade - as in current implementation. 2. ovirt-node reinstall - behaves as host re-install, just perform the host-deploy again. REASONING If ovirt-node was reinstalled, or there was other issues like require to re-enroll certificate, there is no need to upgrade node to different version, just to deploy again. APPENDIXES While doing this work, please also separate the VdsInstallCommand into two commands, once for installation/reinstallation (both node and host), and one for ovirt-node upgrade. These two logics resides within the same command which is invalid.
Hi Ravi, Following bug#1065739, here is more complete work requires to cleanup the host-deploy. Yaniv was to be assigned to this, but maybe it will be easy for you. Thanks, Alon
Please check TCMS plan, if any comments please get in touch. If OK, then reset the flag. Thanks!
The TCMS plan looks good
ok, ovirt-engine-webadmin-portal-3.5.0-0.0.master.20140629172257.git0b16ed7.el6.noarch
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/RHSA-2015-0158.html