Hi, now that oVirt 3.5.0 has been released is time to start planning for 3.5.1. Release management for 3.5.z has been created [1] Suggested schedule for 3.5.1, following the 1 month schedule we had in 3.4.z, are: General availability: 2014-12-02 RC Build: 2014-11-25 A tracker bug for 3.5.1 has been created [2] and shows currently one blocker: Bug ID Whiteboard Status Summary 1145977 infra POST [events] Host memory usage exceeded defined threshold cha... There are 199 bugs [3] targeted to 3.5.1. Excluding node and documentation bugs we still have 170 bugs [4] targeted to 3.5.1. Maintainers / Assignee: - Please add the bugs to the tracker if you think that 3.5.1 should not be released without them fixed. - Please update the target to 3.5.2 or later for bugs that won't be in 3.5.1: it will ease gathering the blocking bugs for next releases. - Please fill release notes, the page has been created here [5] Community: - If you're testing oVirt 3.5 nightly snapshot, please add yourself to the test page [6] [1] http://www.ovirt.org/OVirt_3.5.z_Release_Management [2] http://bugzilla.redhat.com/1155170 [3] http://goo.gl/7G0PDV [4] http://goo.gl/6gUbVr [5] http://www.ovirt.org/OVirt_3.5.1_Release_Notes [6] http://www.ovirt.org/Testing/oVirt_3.5.1_Testing -- Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com
On 22/10/14 08:32, Sandro Bonazzola wrote:
Hi, now that oVirt 3.5.0 has been released is time to start planning for 3.5.1.
Release management for 3.5.z has been created [1] Suggested schedule for 3.5.1, following the 1 month schedule we had in 3.4.z, are:
General availability: 2014-12-02 RC Build: 2014-11-25
A tracker bug for 3.5.1 has been created [2] and shows currently one blocker:
Bug ID Whiteboard Status Summary 1145977 infra POST [events] Host memory usage exceeded defined threshold cha...
As it's a regression from 3.4 I'd sugest https://bugzilla.redhat.com/show_bug.cgi?id=1145241 as a blocker. -- Mit freundlichen Grüßen / Regards Sven Kieske Systemadministrator Mittwald CM Service GmbH & Co. KG Königsberger Straße 6 32339 Espelkamp T: +49-5772-293-100 F: +49-5772-293-333 https://www.mittwald.de Geschäftsführer: Robert Meyer St.Nr.: 331/5721/1033, USt-IdNr.: DE814773217, HRA 6640, AG Bad Oeynhausen Komplementärin: Robert Meyer Verwaltungs GmbH, HRB 13260, AG Bad Oeynhausen
On Wed, Oct 22, 2014 at 1:12 PM, Sven Kieske <s.kieske@mittwald.de> wrote:
On 22/10/14 08:32, Sandro Bonazzola wrote:
Hi, now that oVirt 3.5.0 has been released is time to start planning for 3.5.1.
Release management for 3.5.z has been created [1] Suggested schedule for 3.5.1, following the 1 month schedule we had in 3.4.z, are:
General availability: 2014-12-02 RC Build: 2014-11-25
A tracker bug for 3.5.1 has been created [2] and shows currently one blocker:
Bug ID Whiteboard Status Summary 1145977 infra POST [events] Host memory usage exceeded defined threshold cha...
As it's a regression from 3.4 I'd sugest https://bugzilla.redhat.com/show_bug.cgi?id=1145241 as a blocker.
+1 and in the mean time that 3.5.1 is released it would be nice to provide also a sort of script to create such a default disk profile from console right after engine-setup, so that when running the GUI all is ok. And updating release notes http://www.ovirt.org/OVirt_3.5_Release_Notes inside the section "Install / Upgrade from Previous Versions" Gianluca
On 22/10/14 13:12, Sven Kieske wrote:
As it's a regression from 3.4 I'd sugest https://bugzilla.redhat.com/show_bug.cgi?id=1145241 as a blocker.
To be a little more specific on this topic: This bug got introduced because of incomplete release criteria: "MUST: Fully operational flow (define DC hierarchy so you can run vm) with GUI/CLI/Python-API/REST-API " "MUST: Upgrade from previous release Features/bug list: " from: http://www.ovirt.org/OVirt_3.5_release-management#Release_Criteria_.28WIP.29 So these things get tested independent but not in combination. imho it makes sense to alter the release criteria for 3.6: MUST: Upgrade from previous release MUST: Fully operational flow (define DC hierarchy so you can run vm) with GUI/CLI/Python-API/REST-API This simple automatic test would have revealed the bug before GA: 1. Spin up latest release 2. Upgrade to RC 3. define DC hierarchy so you can run vm HTH -- Mit freundlichen Grüßen / Regards Sven Kieske Systemadministrator Mittwald CM Service GmbH & Co. KG Königsberger Straße 6 32339 Espelkamp T: +49-5772-293-100 F: +49-5772-293-333 https://www.mittwald.de Geschäftsführer: Robert Meyer St.Nr.: 331/5721/1033, USt-IdNr.: DE814773217, HRA 6640, AG Bad Oeynhausen Komplementärin: Robert Meyer Verwaltungs GmbH, HRB 13260, AG Bad Oeynhausen
Il 22/10/2014 13:51, Sven Kieske ha scritto:
On 22/10/14 13:12, Sven Kieske wrote:
As it's a regression from 3.4 I'd sugest https://bugzilla.redhat.com/show_bug.cgi?id=1145241 as a blocker.
To be a little more specific on this topic:
This bug got introduced because of incomplete release criteria:
"MUST: Fully operational flow (define DC hierarchy so you can run vm) with GUI/CLI/Python-API/REST-API "
"MUST: Upgrade from previous release
Features/bug list: "
from:
http://www.ovirt.org/OVirt_3.5_release-management#Release_Criteria_.28WIP.29
So these things get tested independent but not in combination.
imho it makes sense to alter the release criteria for 3.6:
MUST: Upgrade from previous release MUST: Fully operational flow (define DC hierarchy so you can run vm) with GUI/CLI/Python-API/REST-API
This simple automatic test would have revealed the bug before GA:
1. Spin up latest release 2. Upgrade to RC 3. define DC hierarchy so you can run vm
Test case created: http://www.ovirt.org/QA:TestCase_DC_hierarchy Feel free to edit / improve it.
HTH
-- Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com
On 23/10/14 08:49, Sandro Bonazzola wrote:
Il 22/10/2014 13:51, Sven Kieske ha scritto:
On 22/10/14 13:12, Sven Kieske wrote:
As it's a regression from 3.4 I'd sugest https://bugzilla.redhat.com/show_bug.cgi?id=1145241 as a blocker.
To be a little more specific on this topic:
This bug got introduced because of incomplete release criteria:
"MUST: Fully operational flow (define DC hierarchy so you can run vm) with GUI/CLI/Python-API/REST-API "
"MUST: Upgrade from previous release
Features/bug list: "
from:
http://www.ovirt.org/OVirt_3.5_release-management#Release_Criteria_.28WIP.29
So these things get tested independent but not in combination.
imho it makes sense to alter the release criteria for 3.6:
MUST: Upgrade from previous release MUST: Fully operational flow (define DC hierarchy so you can run vm) with GUI/CLI/Python-API/REST-API
This simple automatic test would have revealed the bug before GA:
1. Spin up latest release 2. Upgrade to RC 3. define DC hierarchy so you can run vm
Test case created: http://www.ovirt.org/QA:TestCase_DC_hierarchy Feel free to edit / improve it.
Thank you very much! In fact I will try to spin up some jenkins slaves in the future to roll such test cases automatically (if you can't for some reason). It will take some time until I get there, but I think it saves much time and trouble. -- Mit freundlichen Grüßen / Regards Sven Kieske Systemadministrator Mittwald CM Service GmbH & Co. KG Königsberger Straße 6 32339 Espelkamp T: +49-5772-293-100 F: +49-5772-293-333 https://www.mittwald.de Geschäftsführer: Robert Meyer St.Nr.: 331/5721/1033, USt-IdNr.: DE814773217, HRA 6640, AG Bad Oeynhausen Komplementärin: Robert Meyer Verwaltungs GmbH, HRB 13260, AG Bad Oeynhausen
Il 23/10/2014 15:07, Sven Kieske ha scritto:
On 23/10/14 08:49, Sandro Bonazzola wrote:
Il 22/10/2014 13:51, Sven Kieske ha scritto:
On 22/10/14 13:12, Sven Kieske wrote:
As it's a regression from 3.4 I'd sugest https://bugzilla.redhat.com/show_bug.cgi?id=1145241 as a blocker.
To be a little more specific on this topic:
This bug got introduced because of incomplete release criteria:
"MUST: Fully operational flow (define DC hierarchy so you can run vm) with GUI/CLI/Python-API/REST-API "
"MUST: Upgrade from previous release
Features/bug list: "
from:
http://www.ovirt.org/OVirt_3.5_release-management#Release_Criteria_.28WIP.29
So these things get tested independent but not in combination.
imho it makes sense to alter the release criteria for 3.6:
MUST: Upgrade from previous release MUST: Fully operational flow (define DC hierarchy so you can run vm) with GUI/CLI/Python-API/REST-API
This simple automatic test would have revealed the bug before GA:
1. Spin up latest release 2. Upgrade to RC 3. define DC hierarchy so you can run vm
Test case created: http://www.ovirt.org/QA:TestCase_DC_hierarchy Feel free to edit / improve it.
Thank you very much!
In fact I will try to spin up some jenkins slaves in the future to roll such test cases automatically (if you can't for some reason). It will take some time until I get there, but I think it saves much time and trouble.
I suggest you to work with infra@ovirt.org so we can have the test included in ovirt jenkins :-) -- Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com
Il 22/10/2014 13:12, Sven Kieske ha scritto:
On 22/10/14 08:32, Sandro Bonazzola wrote:
Hi, now that oVirt 3.5.0 has been released is time to start planning for 3.5.1.
Release management for 3.5.z has been created [1] Suggested schedule for 3.5.1, following the 1 month schedule we had in 3.4.z, are:
General availability: 2014-12-02 RC Build: 2014-11-25
A tracker bug for 3.5.1 has been created [2] and shows currently one blocker:
Bug ID Whiteboard Status Summary 1145977 infra POST [events] Host memory usage exceeded defined threshold cha...
As it's a regression from 3.4 I'd sugest https://bugzilla.redhat.com/show_bug.cgi?id=1145241 as a blocker.
Added -- Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi, please consider: https://bugzilla.redhat.com/show_bug.cgi?id=1156115 as a backport to 3.5.1 I don't know if you plan to release a new vdsm version though and I also don't know if this patch is already matured enough, if I can test or help make this patch better, please let me know, as I'm very interested in getting it into this release. kind regards Sven -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQGcBAEBAgAGBQJUSS/jAAoJEAq0kGAWDrqlUHUMAIOkbgi0Ao0vEE6doW4Psxme v0daafB/B3WIRlJBl9vN0FF2vcdevaSk3evmq5vv7S141f9DoYKP5scQLblZHPwh B86V9mcgWGpTs6ms2FXekxnpXSmsaP25kWYUgV5hGJP8QrykYtWZPkD8wDo/Q7Eo t3bUDlGqPO3zAX5SUS5NOdI0KKPOXgihR+kHcl6oHbqKewPWwlrJ6Z7bCcYYBSDf oglwDc4sK1i7Z+6Lx2QrdgXEJehniIIM03AHxO51QSivgJUcWijNvnerWpsV9elN 8w0K8J9CpJ+V9aqk99tuIH3fALNuww1m4phqg+2/nIhr+RYxPrQA1kwE2Jqvr7ey OlY+rjSjkZr4UUV34NqigGZQ3n4x46VTaMNTe4lGcN9AJAxz0U8sdMbG373sm1mt MsgMG8GumfIGTq2Wb8anWrhBWl4hU/MLsQLkHgq49LdIZy4ZU5opxlDRLd+5vgto VUXi0aKsUhIjRpLK3kTsYg2kvwa+2V0mThS62X98aw== =eN0C -----END PGP SIGNATURE-----
----- Original Message -----
From: "Sven Kieske" <svenkieske@gmail.com> To: users@ovirt.org Sent: Thursday, October 23, 2014 6:42:11 PM Subject: Re: [ovirt-users] [QE] oVirt 3.5.1 status
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Hi,
please consider: https://bugzilla.redhat.com/show_bug.cgi?id=1156115 as a backport to 3.5.1
I don't know if you plan to release a new vdsm version though and I also don't know if this patch is already matured enough, if I can test or help make this patch better, please let me know, as I'm very interested in getting it into this release.
Hi Sven, first of all we need to merge the patch in master and yes, as you suggested having some help would speed up the process. The patch affects the move/copy of images with (one or more) snapshots. I already briefly tested the patch with qemu-img from rhel 6 so we need to cover other platforms (fedora and centos) and test: - cold/live move of disks from one storage to another (both nfs/iscsi and cold move from nfs to iscsi and backward) - export vms (with snapshots) to export domain and re-import it (both nfs and iscsi) Once the patch is in master and we have a feedback on how stable it is we may consider it for backporting (maybe 3.5.2 or 3.5.3 if ever). Thanks, -- Federico
participants (5)
-
Federico Simoncelli -
Gianluca Cecchi -
Sandro Bonazzola -
Sven Kieske -
Sven Kieske