Red Hat Bugzilla – Bug 1313304
Libvirt randomly reports different info types when job is cancelled
Last modified: 2016-04-18 06:46:10 EDT
Description of problem:
So I have an Instance that I want to live migrate. I start migration job, but in the middle of the process I decide to abort it. Everything goes fine, I'm getting libvirt error for the migration job:
libvirtError: operation aborted: migration job: canceled by client
and that's okay. However, I'm also checking info type of a running job, and here I'm getting two different values randomly: VIR_DOMAIN_JOB_FAILED and VIR_DOMAIN_JOB_CANCELLED
Version-Release number of selected component (if applicable): 1.2.16
How reproducible: Randomly, looks like a race condition
Steps to Reproduce:
1. Boot a VM
2. Start live migration
3. Abort job
4. Check job info type
5. Sometimes it will report VIR_DOMAIN_JOB_FAILED, and sometimes VIR_DOMAIN_JOB_CANCELLED, while always returning an error that job was cancelled by user
Randomly chosen info type between VIR_DOMAIN_JOB_FAILED and VIR_DOMAIN_JOB_CANCELLED
It always should report VIR_DOMAIN_JOB_CANCELLED
What qemu version is this?
What distro are you using?
When you say randomly, you mean 'random across migration jobs' and not 'random across job info calls', as in once it reports FAILED it always reports FAILED until you try another migration?
It's Ubuntu 15.10 with QEMU 2.3
Yeah, I should have been more specific with what I mean by 'randomly'. Once it reports FAILED it always reports FAILED. Let's say - you aborted two live migration jobs, one reports FAILED (and it always reports FAILED), the other one reports CANCELLED (and it always reports CANCELLED), while both returns an error that job was cancelled by user.