<html>
<head>
<meta content="text/html; charset=UTF-8" http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<div class="moz-cite-prefix">On 01/23/2014 12:32 PM, Sandro
Bonazzola wrote:<br>
</div>
<blockquote cite="mid:52E0BE8E.3060403@redhat.com" type="cite">
<pre wrap="">Il 23/01/2014 07:45, Ramesh Nachimuthu ha scritto:
</pre>
<blockquote type="cite">
<pre wrap="">Hi,
After adding the node to engine, it goes to non operational state with the error "Host 10.70.43.160 is compatible with versions (3.0,3.1,3.2,3.3) and cannot join Cluster Default which is set to version 3.4.".
I have enabled the repo <a class="moz-txt-link-freetext" href="http://resources.ovirt.org/releases/3.4.0_pre/rpm/Fedora/$releasever/">http://resources.ovirt.org/releases/3.4.0_pre/rpm/Fedora/$releasever/</a> in host.
Following is the vdsm version installed in F19 node:
[root@localhost ~]# rpm -qa | grep vdsm
vdsm-cli-4.14.1-2.fc19.noarch
vdsm-4.14.1-2.fc19.x86_64
vdsm-python-4.14.1-2.fc19.x86_64
vdsm-python-zombiereaper-4.14.1-2.fc19.noarch
vdsm-xmlrpc-4.14.1-2.fc19.noarch
vdsm-gluster-4.14.1-2.fc19.noarch
[root@localhost ~]# vdsClient -s 0 getVdsCaps
clusterLevels = ['3.0', '3.1', '3.2', '3.3']
Anything I am missing here?
</pre>
</blockquote>
<pre wrap="">
Same here, if it's not already there, please open a BZ on VDSM.
As temporary workaround, please use cluster with 3.3 cluster level
</pre>
</blockquote>
I have rasied the BZ
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
<a href="https://bugzilla.redhat.com/show_bug.cgi?id=1056918">https://bugzilla.redhat.com/show_bug.cgi?id=1056918.
</a><br>
<br>
But I am not able to create a new Cluster with Compatibility version
3.3 in Gluster only mode. Only compataibility version supported is
3.4.<br>
<br>
Regards,<br>
Ramesh<br>
<a href="https://bugzilla.redhat.com/show_bug.cgi?id=1056918"></a>
<blockquote cite="mid:52E0BE8E.3060403@redhat.com" type="cite">
<pre wrap="">
</pre>
<blockquote type="cite">
<pre wrap="">
Regards,
Ramesh
----- Original Message -----
From: "Sandro Bonazzola" <a class="moz-txt-link-rfc2396E" href="mailto:sbonazzo@redhat.com"><sbonazzo@redhat.com></a>
To: "arch" <a class="moz-txt-link-rfc2396E" href="mailto:arch@ovirt.org"><arch@ovirt.org></a>, "engine-devel" <a class="moz-txt-link-rfc2396E" href="mailto:engine-devel@ovirt.org"><engine-devel@ovirt.org></a>, <a class="moz-txt-link-abbreviated" href="mailto:Users@ovirt.org">Users@ovirt.org</a>
Sent: Wednesday, January 22, 2014 6:37:23 PM
Subject: [ANN] oVirt 3.4.0 Test Day - Tomorrow Jan 23th
Hi all,
tomorrow Jan 23th we'll have oVirt 3.4.0 test day.
On this day all relevant engineers will be online ready to support
any issues you find during install / operating this new release.
Just make sure you have 1 hosts or more to test drive the new release.
If you're curious to see how it works, this is your chance.
Thanks again for everyone who will join us tomorrow!
Location
#ovirt irc channel
Please communicate here to allow others to see any issues
What
In this test day you have a license to kill ;)
Follow the documentation to setup your environment, and test drive the new features.
Please remember we expect to see some issues, and anything you come up with will save a you when you'll install final release
Remember to try daily tasks you'd usually do in the engine, to see there are no regressions.
Write down the configuration you used (HW, console, etc) in the report etherpad[1].
Documentation
Release notes: <a class="moz-txt-link-freetext" href="http://www.ovirt.org/OVirt_3.4.0_release_notes">http://www.ovirt.org/OVirt_3.4.0_release_notes</a>
Features pages links: <a class="moz-txt-link-freetext" href="http://bit.ly/17qBn6F">http://bit.ly/17qBn6F</a>
If you find errors in the wiki please annotate it as well in report etherpad [1]
Prerequisites / recommendations
Use CentOS or RHEL 6.5 only. 6.4 is unsupported due to various issues (sanlock, libvirt, etc).
Use Fedora 19 only. Fedora 20 is unsupported due to various issues (sos, jboss).
Latest RPMs
repository to be enabled for testing the release are listed in the release notes page [2].
NEW issues / reports
For any new issue, please update the reports etherpad [1]
Feature owners, please make sure:
your feature is updated and referenced on release page [2].
you have testing instruction for your feature either on test day page [3] or in your feature page.
your team regression testing section is organized and up to date on test day page [3].
[1] <a class="moz-txt-link-freetext" href="http://etherpad.ovirt.org/p/3.4-testday-1">http://etherpad.ovirt.org/p/3.4-testday-1</a>
[2] <a class="moz-txt-link-freetext" href="http://www.ovirt.org/OVirt_3.4.0_release_notes">http://www.ovirt.org/OVirt_3.4.0_release_notes</a>
[3] <a class="moz-txt-link-freetext" href="http://www.ovirt.org/OVirt_3.4_Test_Day">http://www.ovirt.org/OVirt_3.4_Test_Day</a>
Thanks.
</pre>
</blockquote>
<pre wrap="">
</pre>
</blockquote>
<br>
</body>
</html>