Re: [PATCH] migration: Deprecate redundant query-migrate result @blocked

2021-04-20 Thread Peter Maydell
On Tue, 20 Apr 2021 at 10:25, Dr. David Alan Gilbert wrote: > > * Daniel P. Berrangé (berra...@redhat.com) wrote: > > On Tue, Apr 20, 2021 at 07:19:06AM +0200, Markus Armbruster wrote: > > > Result @blocked is true when and only when result @blocked-reasons is > > > present. It's always non-empty

Re: [PATCH] migration: Deprecate redundant query-migrate result @blocked

2021-04-20 Thread Dr. David Alan Gilbert
* Daniel P. Berrangé (berra...@redhat.com) wrote: > On Tue, Apr 20, 2021 at 07:19:06AM +0200, Markus Armbruster wrote: > > Result @blocked is true when and only when result @blocked-reasons is > > present. It's always non-empty when present. @blocked is redundant. > > It was introduced in commit

Re: [PATCH] migration: Deprecate redundant query-migrate result @blocked

2021-04-20 Thread Daniel P . Berrangé
On Tue, Apr 20, 2021 at 07:19:06AM +0200, Markus Armbruster wrote: > Result @blocked is true when and only when result @blocked-reasons is > present. It's always non-empty when present. @blocked is redundant. > It was introduced in commit 3af8554bd0 "migration: Add blocker > information", and has

[PATCH] migration: Deprecate redundant query-migrate result @blocked

2021-04-19 Thread Markus Armbruster
Result @blocked is true when and only when result @blocked-reasons is present. It's always non-empty when present. @blocked is redundant. It was introduced in commit 3af8554bd0 "migration: Add blocker information", and has not been released. This gives us a chance to fix the interface with minim