Hi,
I just tried to reproduce this locally using your xml file, but all seemed fine. So it doesn't seem like there are any problematic filenames.
Ideally, we could stop nova from cleaning up at the failure point, and then at failure for existance of
/usr/bin/kvm-spice
and contents of
/etc/apparmor.d/libvirt/libvirt-$uuid.files
and existance of every disk file listed in the xml file.
To recap - this happens to you always, or only occasionally? Always on the same host?
Can you edit the bug description at top to point out your Ubuntu release, ppas/cloud-archives in use, and libvirt, nova and qemu package versions?
Chuck, do you have any other ideas?
Hi,
I just tried to reproduce this locally using your xml file, but all seemed fine. So it doesn't seem like there are any problematic filenames.
Ideally, we could stop nova from cleaning up at the failure point, and then at failure for existance of
/usr/bin/kvm-spice
and contents of
/etc/apparmor. d/libvirt/ libvirt- $uuid.files
and existance of every disk file listed in the xml file.
To recap - this happens to you always, or only occasionally? Always on the same host?
Can you edit the bug description at top to point out your Ubuntu release, ppas/cloud-archives in use, and libvirt, nova and qemu package versions?
Chuck, do you have any other ideas?