[ovirt-devel] [ACTION REQUIRED] MUST: No regressions from 3.4 Release

[Piotr Kliczewski]

On Tue, Sep 2, 2014 at 3:29 PM, Sandro Bonazzola <sbonazzo at redhat.com> wrote:
> Il 02/09/2014 15:07, Dan Kenigsberg ha scritto:
>> On Tue, Sep 02, 2014 at 10:30:01AM +0200, Sandro Bonazzola wrote:
>>> The following bugs are keyworded as Regression[1]:
>>>
>>> Whiteboard   Bug ID  Status  Summary
>>> infra                1106435 NEW     [AAA] builtin kerbldap provider does not show error if search fails
>>> infra                1112120 NEW     JSON RPC broker should pass correlation id to VDSM

Above bug is targeted to 3.6. The reason for it was that each jsonrpc
message contains its UUID
so each request/response can be track using it so there is no need to
pass correlation (yet another) id.

>>> infra                1134233 POST    /api/jobs - HTTP Status 500
>>> infra                1131030 NEW     [REST API] using from filter in an event search doesn't work
>>> storage              1116572 NEW     [engine-backend] Storage domain activation isn't executed as part of storage domain creation
>>> storage              1119852 POST    Engine remains indifferent to "Select as SPM" command
>>> ux           1110444 NEW     bookmark selection does not work on first try
>>> ux           1131881 NEW     [GUI]Row item (vms,data-centers,clusters...) mirrored After remove operation
>>> virt         1133995 NEW     vm name field is misaligned on "new vm" pop up window
>>> virt         1120232 NEW     Taking snapshot of vm in suspend state doesn't work
>>>
>>> Please review them and set them as blocker if they're confirmed regressions or drop Regression keyword.
>>> Thanks,
>>
>>  ioprocess's Bug 1130045 - Very high memory consumption
>
> Can you add Regression keyword to the bug?
>
>>
>> should be considered a regression, too - not of ioprocess itself (as the
>> component is new) but of vdsm which uses it. We should not release 3.5.0
>> without fixing this memory leak.
>>
>> Dan.
>>
>
>
> --
> Sandro Bonazzola
> Better technology. Faster innovation. Powered by community collaboration.
> See how it works at redhat.com
> _______________________________________________
> Devel mailing list
> Devel at ovirt.org
> http://lists.ovirt.org/mailman/listinfo/devel