oVirt 3.6 vdsm (4.17.x) won't support el6. Therefore, we have a lot of code that we can drop
Verified in vdsm-4.17.8-1.el7ev (build 3.6.0-15). Code change, verified in automation. Basic regression test suite for hosts passed, list of tests executed: 022-ActivateInactiveHost_REST;activate_inactive_host 023-CreateHostWithEmptyRootPassword_REST;create_host_with_empty_root_password 024-CreateHostWithWrongIPAddress_REST;create_host_with_wrong_IP_address 025-ManualFenceForHost_REST;manual_fence_for_host 026-ReinstallActiveHost_REST;reinstall_active_host 027-ReinstallHost_REST;reinstall_host 028-RemoveActiveHost_REST;remove_active_host 029-SearchForHost_REST;search_for_host 030-SetActiveHostToMaintenanceForReinstallation_REST;set_active_host_to_maintenance 031-SetSPMToLow_REST;set_spm_to_low 032-TestActivateActiveHost_REST;activate_active_host 033-TestUpdateHostName_REST;update_host_name 034-UpdateIPOfActiveHost_REST;update_ip_of_activeHost
Hi Yaniv, Just to clarify, it will still be possible to run RHEL6 hosts under 3.5 compatibility mode in 3.6, but with older vdsm versions, right? However, 3.6 vdsm (4.17.x) won't install/upgrade to on RHEL6 hosts. If you run `yum update vdsm` on the host, it would not bring vdsm.4.17.x and break the system.
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/RHBA-2016-0362.html