Re: [ovirt-users] [QE] oVirt 3.5.1 status

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.