case3: 3.3.3 engine with 3.5 vdsm =================================== vdsm-4.14.1-339.gitedb07b8.el6.x86_64 rhevm-3.3.3-0.51.el6ev.noarch cluster compatibility version 3.2 - host is non operational cluster compatibility version 3.3 - host is non operational select option_name,option_value,version from vdc_options where option_name='SupportedVDSMVersions'; option_name | option_value | version -----------------------+-------------------------+--------- SupportedVDSMVersions | 4.9,4.10,4.11,4.12,4.13 | general case3 3.3 engine with vdsm-4.13 (3.3): ================================== vdsm-4.13.2-0.16.el6ev.x86_64 rhevm-3.3.3-0.51.el6ev.noarch cluster compatibility version 3.2 - host is UP cluster compatibility version 3.3 - host is UP select option_name,option_value,version from vdc_options where option_name='SupportedVDSMVersions'; option_name | option_value | version -----------------------+-------------------------+--------- SupportedVDSMVersions | 4.9,4.10,4.11,4.12,4.13 | general
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-2014-0547.html
*** Bug 1109912 has been marked as a duplicate of this bug. ***