============ RFE REQUEST =============== 1. Proposed title of this feature request [RFE] "yum update" a RHEL Hypervisor through the RHEV Webinterface(RHEVM) 3. What is the nature and description of the request? > Customer wants to "yum update" a RHEL Hypervisor through the RHEV Webinterface. It should then also use the during the bootstrap phase (RHEV WebUI added Host) distributed SSH Key. 4. Why does the customer need this? (List the business requirements here) > Customer reply: To update a RHEL-Host safely to the highest supported version. For example if we use RHEV 3.2 and RHEL 6.10 is GA, but not supported on RHEV 3.2 we only want to update to 6.9 latest so we stick with a supported RHEL-Host for RHEV. 5. How would the customer like to achieve this? (List the functional requirements here) > Customer reply: Technical implementation has to be decided by Red Hat Engineering. 6. For each functional requirement listed, specify how Red Hat and the customer can test to confirm the requirement is successfully implemented. 7. Is there already an existing RFE upstream or in Red Hat Bugzilla? 8. Does the customer have any specific timeline dependencies and which release would they like to target (i.e. RHEL5, RHEL6)? > No 9. Is the sales team involved in this request and do they have any additional input? 10. List any affected packages or components. 11. Would the customer be able to assist in testing this functionality if implemented? > Yes
rhel and vdsm [should] are backward compatibly. there should be no problem to issue 'yum update' using any rhel based provisioning tool to update to latest.
I suggest to close this RFE as WONTFIX, per comment#2. There are tools like satellite and such to perform these tasks.
Moving needinfo to current RHEV PM.
*** This bug has been marked as a duplicate of bug 1016839 ***
Removing old needinfos. Please restore, if still needed.