On Thu, Feb 11, 2016 at 5:38 PM, Chris Adams <cma(a)cmadams.net> wrote:
Once upon a time, Chris Adams <cma(a)cmadams.net> said:
> On oVirt 3.6.2, I tried to clone a VM, but got an error that the volume
> couldn't be created. Checking the logs, I see (in vdsm.log on the SPM):
>
> jsonrpc.Executor/2::ERROR::2016-02-11
09:50:24,459::dispatcher::76::Storage.Dispatcher::(wrapper) {'status':
{'message': "Image is not a legal chain:
(u'fa4d1802-6223-4800-8339-c194076cfb4b',)", 'code': 262}}
>
> The VM I am trying to clone is thin-provisioned from a template; is it
> "legal" to clone such a VM, or is this a bug?
Hmm, weird; I also tried just copying the disk, and I could not.
Fiddling around, I forced SPM over to another node, and copy worked, so
I tried cloning again, and that worked too. Guess something needed a
"reset".
Do you have the logs from the original spm? Checking them may explain why
the chain was legal.
Sound like an operation was interrupted, and it took some time to clean up
chain, but this is only a guess.
Nir