5:01 p.m.
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
5:46 p.m.
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:
--
Paul Dyer,
Mercury Consulting Group, RHCE
504-302-8750
10:57 a.m.
--Apple-Mail=_ECD3F43B-AB35-41DB-A461-3D6F3469ECE3
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
charset=us-ascii
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.
the latter is not a correct solution and should not be encouraged.
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.
<mailto:pmdyermms@gmail.com>> wrote:
Hi,
=20
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?
=20
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.
--Apple-Mail=_ECD3F43B-AB35-41DB-A461-3D6F3469ECE3
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
charset=us-ascii
<html><head><meta http-equiv=3D"Content-Type"
content=3D"text/html =
charset=3Dus-ascii"></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" =
class=3D""><br class=3D""><div><blockquote
type=3D"cite" class=3D""><div =
class=3D"">On 20 Feb 2016, at 17:46, Paul Dyer <<a =
href=3D"mailto:pmdyermms@gmail.com"
class=3D"">pmdyermms(a)gmail.com</a>&gt;=
wrote:</div><br class=3D"Apple-interchange-newline"><div
class=3D""><div =
dir=3D"ltr" class=3D"">It seems like I am hitting this issue from
=
release 3.6.0:<div class=3D""><br
class=3D""></div><div class=3D""><ul =
style=3D"margin-top:0px;margin-bottom:8.5pt;color:rgb(51,51,51);font-famil=
y:'Source Sans Pro','Open Sans','Helvetica =
Neue',Helvetica,Arial,sans-serif;font-size:16px;line-height:22.8571px" =
class=3D""><li class=3D"">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.</li></ul></div></div></div></blockquote><div><br
=
class=3D""></div>the latter is not a correct solution and should not be
=
encouraged.</div><div><br class=3D""><blockquote
type=3D"cite" =
class=3D""><div class=3D""><div dir=3D"ltr"
class=3D""><div =
class=3D""><div class=3D"">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.<br =
class=3D""></div></div><div class=3D""><br
class=3D""></div><div =
class=3D"">Paul</div></div><div
class=3D"gmail_extra"><br class=3D""><div =
class=3D"gmail_quote">On Sat, Feb 20, 2016 at 10:01 AM, Paul Dyer <span =
dir=3D"ltr" class=3D""><<a
href=3D"mailto:pmdyermms@gmail.com" =
target=3D"_blank"
class=3D"">pmdyermms(a)gmail.com</a>&gt;</span> =
wrote:<br class=3D""><blockquote class=3D"gmail_quote"
style=3D"margin:0 =
0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div
dir=3D"ltr" =
class=3D"">Hi,<div class=3D""><br
class=3D""></div><div class=3D"">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?</div><div class=3D""><br =
class=3D""></div><div class=3D"">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.</div><div class=3D""><br
class=3D""></div><div class=3D"">Thanks =
a million,</div><div class=3D""><br
class=3D""></div><div =
class=3D"">Paul</div><span class=3D"HOEnZb"><font
color=3D"#888888" =
class=3D""><div class=3D""><br
class=3D""></div><div class=3D""><br =
class=3D""></div><div class=3D""><div
class=3D""><br class=3D""></div>-- =
<br class=3D""><div class=3D"">Paul Dyer,<br
class=3D"">Mercury =
Consulting Group, RHCE<br class=3D""><a
href=3D"tel:504-302-8750" =
value=3D"+15043028750" target=3D"_blank"
class=3D"">504-302-8750</a></div>=
</div></font></span></div>
</blockquote></div><br class=3D""><br
clear=3D"all" class=3D""><div =
class=3D""><br class=3D""></div>-- <br
class=3D""><div =
class=3D"gmail_signature">Paul Dyer,<br class=3D"">Mercury
Consulting =
Group, RHCE<br class=3D"">504-302-8750</div>
</div>
_______________________________________________<br class=3D"">Devel =
mailing list<br class=3D""><a href=3D"mailto:Devel@ovirt.org"
=
class=3D"">Devel(a)ovirt.org</a><br =
class=3D"">http://lists.ovirt.org/mailman/listinfo/devel<...
</div><br class=3D""></body></html>=
--Apple-Mail=_ECD3F43B-AB35-41DB-A461-3D6F3469ECE3--
7:32 p.m.
Hi Paul,
The 'reinstall' will attempt to install the latest version of vdsm, it will
enroll certificates for the host and more, but if the host was already
installed in the system, it will not attempt to re-configure the network.
In your case, there seems to be a mismatch between the repositories (of
yum) configured on the host to the cluster level.
In order to support the host within 3.6 cluster, the host should have the
3.6 repo configured (http://resources.ovirt.org/pub/yum-repo/)
Then 'reinstall' will update the latest version of 'vdsm' and will
configure it.
Regards,
Moti
On Sat, Feb 20, 2016 at 6:01 PM, Paul Dyer <pmdyermms(a)gmail.com> wrote:
--
Regards,
Moti
1:06 a.m.
Moti,
Thanks for the info. In my case, the engine host is different from the
virtualization host (where the VMs run). Should the virtualization host
also have the 3.6 repo, just like the engine host?
Thanks,
Paul
On Sun, Feb 21, 2016 at 12:32 PM, Moti Asayag <masayag(a)redhat.com> wrote:
--
Paul Dyer,
Mercury Consulting Group, RHCE
504-302-8750
10:50 p.m.
Hi,
this a late reply. When I look through the repo you listed, I only see
vdsm rpm in the ovirt-3.5 area for el6.6.
Has there been no vdsm changes for ovirt-3.6?
Paul
On Sun, Feb 21, 2016 at 12:32 PM, Moti Asayag <masayag(a)redhat.com> wrote:
--
Paul Dyer,
Mercury Consulting Group, RHCE
504-302-8750
11 a.m.
+Eyal and Sandro
Could you list the exact repo ([1] ?) which should be configured on the
host for 3.6 cluster support ?
[1] http://resources.ovirt.org/pub/yum-repo/ovirt-release36.rpm
On Fri, Mar 11, 2016 at 11:50 PM, Paul Dyer <pmdyermms(a)gmail.com> wrote:
--
Regards,
Moti
11:22 a.m.
On Sun, Mar 13, 2016 at 12:00 PM, Moti Asayag <masayag(a)redhat.com> wrote:
3.6 does not support el6 hosts and does not ship RPMs for el6.
A 3.6 engine can still manage existing 3.5/el6 hosts at 3.5 compatibility level.
To upgrade hosts to 3.6, you'll need to reinstall them with el7.
Best,
--
Didi
1:01 p.m.
On Sun, Mar 13, 2016 at 10:22 AM, Yedidyah Bar David <didi(a)redhat.com>
wrote:
Indeed.
The repos for vdsm 3.6 (el7 only) can be found here:
http://resources.ovirt.org/pub/ovirt-3.6/rpm/el7
--
Eyal Edri
Associate Manager
EMEA ENG Virtualization R&D
Red Hat Israel
phone: +972-9-7692018
irc: eedri (on #tlv #rhev-dev #rhev-integ)
4:14 p.m.
Thanks all. I was able to install RHEL 7.2 on the virtualization host
Friday. ovirt 3.6.3 now works as expected. The VM console works again
for spice/rdesktop clients.
Thanks,
Paul
On Sun, Mar 13, 2016 at 10:26 AM, Paul Dyer <pmdyermms(a)gmail.com> wrote:
--
Paul Dyer,
Mercury Consulting Group, RHCE
504-302-8750
3342
days inactive
3378
days old
10 comments
5 participants
participants (5)
-
Eyal Edri -
Michal Skrivanek -
Moti Asayag -
Paul Dyer -
Yedidyah Bar David