On 6 May 2014, at 12:12, Sandro Bonazzola wrote:
Il 06/05/2014 11:34, Juan Hernandez ha scritto:
On 05/06/2014 11:22 AM, Sven Kieske wrote:
Thanks for the answer and for fixing the error reporting path. Will there be a respin of the RC or will it just get included into 3.4.1 GA ?
I'm trying to get it into 3.4.1 GA, and as the bug is currently a blocker 3.4.1 GA won't be released without it. I think that we aren't doing a respin of the RC.
We'll wait for it in order to release 3.4.1 GA, no RC respin planned.
Since it's "only" about a proper error message in case of invalid json, I don't think it should be a blocker…. If there is nothing else pending IMHO we should go ahead with the release, 3.4.2 is not that far away… Thanks, michal
Am 06.05.2014 10:36, schrieb Juan Hernandez:
Ok, I assumed that you were creating a VM, not starting it.
The main difference between that JSON and the one I sent previously is the outer "vm" element. The reason for that is that starting a VM is different than creating it. Creating receives a VM entity as parameter, so it doesn't need the outer "vm" element. Starting doesn't receive a VM, but an Action entity, and the VM is just a member of that action. The outer "action" element isn't needed. Taking that into account your JSON is correct.
I don't see other differences. Did I miss something?
Anyhow, there is still a bug in the error reporting path. That needs to be fixed.
-- Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com _______________________________________________ Devel mailing list Devel@ovirt.org http://lists.ovirt.org/mailman/listinfo/devel