I believe I have significantly relevant information to help isolate the problem and I do
believe it is a bug.
First, I previously said that "all exported VMs" were affected. That is
incorrect and therefore misleading. I apologize.
The problem at hand appears to have to do with preallocated vs thin provisioning of
disks.
Again, I am running oVirt 4.4.4 at the moment.
All VMs that only have preallocated disks have the problem. When they were exported, the
disk profile remained the original profile from the source data domain. Thus, the error
"Cannot add VM. Cannot find a disk profile defined on storage domain" when
trying to re-export them back the other direction.
VMs that have only thin provisioned disks or a combination of both types do NOT have the
problem. When exported, all disks get the disk profile from the destination domain.
Re-exporting them back the other direction works.
Please let me know if I correctly identified a bug. More importantly, please let me know
if it has been fixed since 4.4.4 and what I can do in the mean time. I really need to
"restore" one of my VMs that is stuck in limbo because of the incorrect disk
profile.
Your prompt response is greatly appreciated.