libvirt users - Mar 2017 - Re: VIR_ERR_OPERATION_INVALID from virDomainDestroyFlags call

Hi, we experienced a strange, non-reproducible error after a successful
migration to another host.  When we called virDomainDestroyFlags with
VIR_DOMAIN_DESTROY_GRACEFUL flag after the migration on the source host,
we got VIR_ERR_OPERATION_INVALID (code 55) error.  The same with
repeated virDomainDestroyFlags calls.  Normally, we would expect either
success or VIR_ERR_NO_DOMAIN error.  `virsh list' didn't show the VM.

Can anybody please explain to us when this can happen and what the error
means in this context?  When we have good reasons to believe that the VM
is down (e.g. after a migration call successfully finishes) and we
receive such an error from virDomainDestroyFlags, is it safe to assume
the VM is basically gone and can we perform standard cleanup actions
(like removing related files from the host file system)?

Thank you,
Milan

On Fri, Mar 17, 2017 at 11:55:13AM +0100, Milan Zamazal
wrote:
> Hi, we experienced a strange, non-reproducible error after a successful
> migration to another host.  When we called virDomainDestroyFlags with
> VIR_DOMAIN_DESTROY_GRACEFUL flag after the migration on the source host,
> we got VIR_ERR_OPERATION_INVALID (code 55) error.  The same with
> repeated virDomainDestroyFlags calls.  Normally, we would expect either
> success or VIR_ERR_NO_DOMAIN error.  `virsh list' didn't show the
VM.
What about 'virsh list --all' - i expect you have an inactive guest
present, as calling destory on an inactive guest triggers OPERATION_INVALID

Regards,
Daniel
-- 
|: http://berrange.com      -o-    http://www.flickr.com/photos/dberrange/ :|
|: http://libvirt.org              -o-             http://virt-manager.org :|
|: http://entangle-photo.org       -o-    http://search.cpan.org/~danberr/ :|

"Daniel P. Berrange" <berrange@redhat.com> writes:
> On Fri, Mar 17, 2017 at 11:55:13AM +0100, Milan Zamazal wrote:
>> Hi, we experienced a strange, non-reproducible error after a successful
>> migration to another host.  When we called virDomainDestroyFlags with
>> VIR_DOMAIN_DESTROY_GRACEFUL flag after the migration on the source
host,
>> we got VIR_ERR_OPERATION_INVALID (code 55) error.  The same with
>> repeated virDomainDestroyFlags calls.  Normally, we would expect either
>> success or VIR_ERR_NO_DOMAIN error.  `virsh list' didn't show
the VM.
>
> What about 'virsh list --all' - i expect you have an inactive guest
> present, as calling destory on an inactive guest triggers OPERATION_INVALID
I see.  It's interesting, since we use transient domains.  Are there
known circumstances when OPERATION_INVALID could be returned for a
transient domain?  Can we assume that we never receive that error when
trying to destroy a running domain?

Thanks,
Milan