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.

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

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.

-----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-----