[Users] [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: http://www.ovirt.org/OVirt_3.4.0_release_notes Features pages links: http://bit.ly/17qBn6F 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] http://etherpad.ovirt.org/p/3.4-testday-1 [2] http://www.ovirt.org/OVirt_3.4.0_release_notes [3] http://www.ovirt.org/OVirt_3.4_Test_Day Thanks. -- Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com

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 http://resources.ovirt.org/releases/3.4.0_pre/rpm/Fedora/$releasever/ 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? Regards, Ramesh ----- Original Message ----- From: "Sandro Bonazzola" <sbonazzo@redhat.com> To: "arch" <arch@ovirt.org>, "engine-devel" <engine-devel@ovirt.org>, Users@ovirt.org 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: http://www.ovirt.org/OVirt_3.4.0_release_notes Features pages links: http://bit.ly/17qBn6F 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] http://etherpad.ovirt.org/p/3.4-testday-1 [2] http://www.ovirt.org/OVirt_3.4.0_release_notes [3] http://www.ovirt.org/OVirt_3.4_Test_Day Thanks. -- Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com _______________________________________________ Arch mailing list Arch@ovirt.org http://lists.ovirt.org/mailman/listinfo/arch

Il 23/01/2014 07:45, Ramesh Nachimuthu ha scritto:
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 http://resources.ovirt.org/releases/3.4.0_pre/rpm/Fedora/$releasever/ 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?
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
Regards, Ramesh ----- Original Message ----- From: "Sandro Bonazzola" <sbonazzo@redhat.com> To: "arch" <arch@ovirt.org>, "engine-devel" <engine-devel@ovirt.org>, Users@ovirt.org 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: http://www.ovirt.org/OVirt_3.4.0_release_notes Features pages links: http://bit.ly/17qBn6F 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] http://etherpad.ovirt.org/p/3.4-testday-1 [2] http://www.ovirt.org/OVirt_3.4.0_release_notes [3] http://www.ovirt.org/OVirt_3.4_Test_Day
Thanks.
-- Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com

This is a multi-part message in MIME format. --------------070006020206010509020909 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit On 01/23/2014 12:32 PM, Sandro Bonazzola wrote:
Il 23/01/2014 07:45, Ramesh Nachimuthu ha scritto:
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 http://resources.ovirt.org/releases/3.4.0_pre/rpm/Fedora/$releasever/ 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? 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 I have rasied the BZ https://bugzilla.redhat.com/show_bug.cgi?id=1056918. <https://bugzilla.redhat.com/show_bug.cgi?id=1056918>
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. Regards, Ramesh <https://bugzilla.redhat.com/show_bug.cgi?id=1056918>
Regards, Ramesh ----- Original Message ----- From: "Sandro Bonazzola" <sbonazzo@redhat.com> To: "arch" <arch@ovirt.org>, "engine-devel" <engine-devel@ovirt.org>, Users@ovirt.org 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: http://www.ovirt.org/OVirt_3.4.0_release_notes Features pages links: http://bit.ly/17qBn6F 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] http://etherpad.ovirt.org/p/3.4-testday-1 [2] http://www.ovirt.org/OVirt_3.4.0_release_notes [3] http://www.ovirt.org/OVirt_3.4_Test_Day
Thanks.
--------------070006020206010509020909 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit <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> --------------070006020206010509020909--

Il 23/01/2014 09:18, Ramesh ha scritto:
On 01/23/2014 12:32 PM, Sandro Bonazzola wrote:
Il 23/01/2014 07:45, Ramesh Nachimuthu ha scritto:
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 http://resources.ovirt.org/releases/3.4.0_pre/rpm/Fedora/$releasever/ 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? 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 I have rasied the BZ https://bugzilla.redhat.com/show_bug.cgi?id=1056918. <https://bugzilla.redhat.com/show_bug.cgi?id=1056918>
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.
Can you try upgrading libvirt* from ftp://libvirt.org/libvirt/ or http://fedorapeople.org/groups/virt/virt-preview/fedora-19/rpms/ ?
Regards, Ramesh <https://bugzilla.redhat.com/show_bug.cgi?id=1056918>
Regards, Ramesh ----- Original Message ----- From: "Sandro Bonazzola" <sbonazzo@redhat.com> To: "arch" <arch@ovirt.org>, "engine-devel" <engine-devel@ovirt.org>, Users@ovirt.org 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: http://www.ovirt.org/OVirt_3.4.0_release_notes Features pages links: http://bit.ly/17qBn6F 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] http://etherpad.ovirt.org/p/3.4-testday-1 [2] http://www.ovirt.org/OVirt_3.4.0_release_notes [3] http://www.ovirt.org/OVirt_3.4_Test_Day
Thanks.
-- Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com

This is a multi-part message in MIME format. --------------030607000302010208070609 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit On 01/23/2014 01:48 PM, Ramesh wrote:
On 01/23/2014 12:32 PM, Sandro Bonazzola wrote:
Il 23/01/2014 07:45, Ramesh Nachimuthu ha scritto:
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 repohttp://resources.ovirt.org/releases/3.4.0_pre/rpm/Fedora/$releasever/ 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? 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 I have rasied the BZ https://bugzilla.redhat.com/show_bug.cgi?id=1056918. <https://bugzilla.redhat.com/show_bug.cgi?id=1056918>
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.
Raised another bug https://bugzilla.redhat.com/show_bug.cgi?id=1056936 for the above issue in Gluster Only mode.
Regards, Ramesh
Regards, Ramesh ----- Original Message ----- From: "Sandro Bonazzola"<sbonazzo@redhat.com> To: "arch"<arch@ovirt.org>, "engine-devel"<engine-devel@ovirt.org>,Users@ovirt.org 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:http://www.ovirt.org/OVirt_3.4.0_release_notes Features pages links:http://bit.ly/17qBn6F 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]http://etherpad.ovirt.org/p/3.4-testday-1 [2]http://www.ovirt.org/OVirt_3.4.0_release_notes [3]http://www.ovirt.org/OVirt_3.4_Test_Day
Thanks.
--------------030607000302010208070609 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit <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 01:48 PM, Ramesh wrote:<br> </div> <blockquote cite="mid:52E0D055.4000402@redhat.com" type="cite"> <meta content="text/html; charset=UTF-8" http-equiv="Content-Type"> <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 moz-do-not-send="true" 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 moz-do-not-send="true" 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> </blockquote> Raised another bug <meta http-equiv="content-type" content="text/html; charset=UTF-8"> <a href="https://bugzilla.redhat.com/show_bug.cgi?id=1056936">https://bugzilla.redhat.com/show_bug.cgi?id=1056936</a> for the above issue in Gluster Only mode.<br> <br> <blockquote cite="mid:52E0D055.4000402@redhat.com" type="cite"> Regards,<br> Ramesh<br> <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 moz-do-not-send="true" class="moz-txt-link-rfc2396E" href="mailto:sbonazzo@redhat.com"><sbonazzo@redhat.com></a> To: "arch" <a moz-do-not-send="true" class="moz-txt-link-rfc2396E" href="mailto:arch@ovirt.org"><arch@ovirt.org></a>, "engine-devel" <a moz-do-not-send="true" class="moz-txt-link-rfc2396E" href="mailto:engine-devel@ovirt.org"><engine-devel@ovirt.org></a>, <a moz-do-not-send="true" 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 moz-do-not-send="true" 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 moz-do-not-send="true" 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 moz-do-not-send="true" 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 moz-do-not-send="true" 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 moz-do-not-send="true" 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> </blockquote> <br> </body> </html> --------------030607000302010208070609--

/top posting/ Guys, please make sure to report the issues in this pad: http://etherpad.ovirt.org/p/3.4-testday-1 and possible work-arounds. This will help everyone else who hits the same issues. Thanks. ----- Original Message -----
From: "Ramesh" <rnachimu@redhat.com> To: "Sandro Bonazzola" <sbonazzo@redhat.com> Cc: Users@ovirt.org Sent: Thursday, January 23, 2014 10:41:53 AM Subject: Re: [Users] [ANN] oVirt 3.4.0 Test Day - Tomorrow Jan 23th
On 01/23/2014 01:48 PM, Ramesh wrote:
On 01/23/2014 12:32 PM, Sandro Bonazzola wrote:
Il 23/01/2014 07:45, Ramesh Nachimuthu ha scritto:
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 http://resources.ovirt.org/releases/3.4.0_pre/rpm/Fedora/$releasever/ 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? 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 I have rasied the BZ https://bugzilla.redhat.com/show_bug.cgi?id=1056918.
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.
Raised another bug https://bugzilla.redhat.com/show_bug.cgi?id=1056936 for the above issue in Gluster Only mode.
Regards, Ramesh
Regards, Ramesh ----- Original Message ----- From: "Sandro Bonazzola" <sbonazzo@redhat.com> To: "arch" <arch@ovirt.org> , "engine-devel" <engine-devel@ovirt.org> , Users@ovirt.org 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: http://www.ovirt.org/OVirt_3.4.0_release_notes Features pages links: http://bit.ly/17qBn6F 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] http://etherpad.ovirt.org/p/3.4-testday-1 [2] http://www.ovirt.org/OVirt_3.4.0_release_notes [3] http://www.ovirt.org/OVirt_3.4_Test_Day Thanks.
_______________________________________________ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users

--=-wuhtaJX6y2vkCeylTlGe Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Am Mittwoch, den 22.01.2014, 14:07 +0100 schrieb Sandro Bonazzola:
Latest RPMs repository to be enabled for testing the release are listed in the release notes page [2].
Hey, the following oVirt Node ISO (based on CentOS 6.5 and oVirt 3.4 components) can be used for the Test Day: http://fedorapeople.org/~fabiand/node/3.0.4/ovirt-node-iso-3.0.4-TestDay.vd= sm.el6.iso Important: You need to append enforcing=3D0 to the kernel when booting the ISO to prevent SELinux denials. Please provide your audit.log after the Test Day by replying to this email. Greetings fabian --=-wuhtaJX6y2vkCeylTlGe Content-Type: application/pgp-signature; name="signature.asc" Content-Description: This is a digitally signed message part Content-Transfer-Encoding: 7bit -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.15 (GNU/Linux) iQIcBAABAgAGBQJS4OVyAAoJEC9+uOgSHVGUpMwP/2OmcaxJS+dJKicYo3ihAIed dwnpCu1dNtiy/QxmnQ2yEb96QZRgKt2WL80Mk78+qbLvcF2P4YzwVhO27n+j/VL1 S2Wt415yiPcNPrDloTeRFS5FLFd4h63y94jZi+O9jwRT0/qt7DdHOWAueH4MU60e 1jiDt2vnrf3MVAg1Wnpxl3qQRtjKbEMDyFr5HDPP3cccdRiXshNRvfw2RjQi59dg Yv5wKAvsOCHnj1fcHakKbae+AcfeMcfMOtb0P4p6fCyj14abTJw9QMKBf2ZzwAxo zLO5E7EMYqiHarOMul32nWIN4uqauVcJFBw817kAw+p4i0DczFrJz7XKPCKMapvv FDiG021phpmp3dfBqyXIZLcq5TwqSPtPDBTch/3BPlkMiRW2RjytZhZcYsLCGaw5 5jNmXF+Tjr1BDdENyxmjXc7Slm2LQSOOviuZ2eUrhlsCgcZEIpvj6fb5Dvf3yM+I 6TXI44z2/VxwIdX9isp/SMlqsa5rXYAp1CToGgtq+9hoSvU7Q2mBIpZoK3Cnby70 cAiy3PffkoH6cPSR+cwY0GELTlWkAoc3x+HKRYZcoT1O8NvSh3e7YTx+QIlKGLhK bg8HT46Nu/XkojXgSxZKf1DGGfJ2PaNj3y+ZmYXT5JcrGm6ocV7c3GDhVF+knrZX p6MXgwUrziule+n/uuXH =sfOU -----END PGP SIGNATURE----- --=-wuhtaJX6y2vkCeylTlGe--

On Thu, 2014-01-23 at 10:48 +0100, Fabian Deutsch wrote:
Am Mittwoch, den 22.01.2014, 14:07 +0100 schrieb Sandro Bonazzola:
Latest RPMs repository to be enabled for testing the release are listed in the release notes page [2].
Hey,
the following oVirt Node ISO (based on CentOS 6.5 and oVirt 3.4 components) can be used for the Test Day: http://fedorapeople.org/~fabiand/node/3.0.4/ovirt-node-iso-3.0.4-TestDay.vds...
Important: You need to append enforcing=0 to the kernel when booting the ISO to prevent SELinux denials.
Is this the only node iso supported for the current 3.4 beta? I also see another iso in the release tree: http://resources.ovirt.org/releases/3.4.0-beta/iso/ovirt-node-iso-3.1.0-0.99... But that is Fedora 18 which is EOL already. Kind regards Jorick Astrego Netbulae B.V.

----- Original Message -----
On Thu, 2014-01-23 at 10:48 +0100, Fabian Deutsch wrote:
Am Mittwoch, den 22.01.2014, 14:07 +0100 schrieb Sandro Bonazzola:
Latest RPMs repository to be enabled for testing the release are listed in the release notes page [2].
Hey,
the following oVirt Node ISO (based on CentOS 6.5 and oVirt 3.4 components) can be used for the Test Day: http://fedorapeople.org/~fabiand/node/3.0.4/ovirt-node-iso-3.0.4-TestDay.vds...
Important: You need to append enforcing=0 to the kernel when booting the ISO to prevent SELinux denials.
Is this the only node iso supported for the current 3.4 beta?
Hey Jorick, Yes, that is currently the only ISO. But right now we are working on a new ISO fixing these two bugs: https://bugzilla.redhat.com/show_bug.cgi?id=1057064 https://bugzilla.redhat.com/show_bug.cgi?id=1057050
I also see another iso in the release tree:
http://resources.ovirt.org/releases/3.4.0-beta/iso/ovirt-node-iso-3.1.0-0.99...
But that is Fedora 18 which is EOL already.
yes - that is a very old build from a couple of months ago - please ignore it. Once we have one stable node around we'll also be providing Fedora based nodes again. - fabian

Il 22/01/2014 14:07, Sandro Bonazzola ha scritto:
Hi all, tomorrow Jan 23th we'll have oVirt 3.4.0 test day.
Hi all, Just wanted to say a big THANK YOU to all participants! -- Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com
participants (7)
-
Doron Fediuck
-
Fabian Deutsch
-
Fabian Deutsch
-
Jorick Astrego
-
Ramesh
-
Ramesh Nachimuthu
-
Sandro Bonazzola