Learn more about these different git repos.
Other Git URLs
It seems like it mostly happens on aarch64 machines, but has also been seen on ppc64le.
ApplianceError: Image status is FAILED: could not create appliance through libvirt. Try running qemu directly without libvirt using this environment variable: export LIBGUESTFS_BACKEND=direct Original error from libvirt: File exists [code=89 int1=0]
Examples where we have seen this:
can we get some multi-arch specialists to look at this? @pwhalen ?
This is not related to multi-arch (note that https://koji.fedoraproject.org/koji/taskinfo?taskID=25858017 is x86_64). I think that this is a race condition in Oz between cleaning up the previous step and creating the guestfs VM for the next step, where it can't create the new VM because the old one hasn't been entirely cleaned up yet but when it goes then look up the old one, that one's been cleaned up.
This is not related to multi-arch (note that https://koji.fedoraproject.org/koji/taskinfo?taskID=25858017 is x86_64).
You are right. I didn't catch that. Most of the ones I have seen were on aarch64 so I was thinking it could have been related.
I think that this is a race condition
Yeah probably. Sucks that we just started seeing it happen more often. Or maybe it's been happening for a while now and we just started looking closer at the results of failable artifacts.
Another example from today: tracker task
Another example from yesterday: tracker task
this continues to be a problem:
Probably we should take it to Oz.
https://pagure.io/dusty/failed-composes/issue/230
This has been fixed. If it's still an issue, please reopen this ticket.
Metadata Update from @syeghiay: - Issue close_status updated to: Fixed - Issue status updated to: Closed (was: Open)
Login to comment on this ticket.