It seems like I am hitting this issue from release 3.6.0:
- If cluster is updated to compatibility version 3.6 while hosts that
have not been upgraded, i.e with emulated machine flags that do not match
cluster compatibility version 3.6, you might end up with incorrect emulated
machine flag on the cluster. As a result, you will not be able to run VMs.
Possible workarounds would be to to reset the emulated machine on the
cluster (requires putting all the hosts into maintenance) or disable the
host-plug memory feature in the database.
I clicked "reset emulated machines" on the cluster, while in maintenance
mode. I checked vds_dynamic for the host, and found the columns
supported_cluster_levels and supported_engine_levels to both be missing
version 3.6.
Paul
On Sat, Feb 20, 2016 at 10:01 AM, Paul Dyer <pmdyermms(a)gmail.com> wrote:
Hi,
can anyone explain what this button does? I have looked in the
documentation but have found no reference to it. Will reinstall only
install packages and setting for the host, and leave
cluster/storage/networks alone?
I have a cluster version 3.6.2 that will not Activate the host because the
message "Host .. is compatible with versions (3.0,3.1,3.2,3.3,3.4,3.5) and
cannot join Cluster...". The host was part of a 3.5 cluster until the
upgrade to 3.6.2.
Thanks a million,
Paul
--
Paul Dyer,
Mercury Consulting Group, RHCE
504-302-8750
--
Paul Dyer,
Mercury Consulting Group, RHCE
504-302-8750