On Thu, May 26, 2016 at 09:00:12AM -0600, Eric Blake wrote: > On 05/26/2016 12:12 AM, Amit Shah wrote: > > From: "Daniel P. Berrange" <berra...@redhat.com> > > > > Currently if an application initiates an outgoing migration, > > it may or may not, get an error reported back on failure. If > > the error occurs synchronously to the 'migrate' command > > execution, the client app will see the error message. This > > is the case for DNS lookup failures. If the error occurs > > asynchronously to the monitor command though, the error > > will be thrown away and the client left guessing about > > what went wrong. This is the case for failure to connect > > to the TCP server (eg due to wrong port, or firewall > > rules, or other similar errors). > > > > > +++ b/qapi-schema.json > > @@ -484,6 +484,10 @@ > > # throttled during auto-converge. This is only present when > > auto-converge > > # has started throttling guest cpus. (Since 2.7) > > # > > +# @error-desc: #optional the human readable error description string, when > > +# @status is 'failed'. Clients should not attempt to parse the > > +# error strings. (Since 2.6) > > Since this is already in a pull request, we may need a followup patch to > fix that to be 2.7.
Yep, taking care of that now. Regards, Daniel -- |: http://berrange.com -o- http://www.flickr.com/photos/dberrange/ :| |: http://libvirt.org -o- http://virt-manager.org :| |: http://autobuild.org -o- http://search.cpan.org/~danberr/ :| |: http://entangle-photo.org -o- http://live.gnome.org/gtk-vnc :|
