Description of problem: string not formatted correctly Error while executing action: Cannot ${action} ${type} Version-Release number of selected component (if applicable): vt16.6 How reproducible: Steps to Reproduce: 1.There was some problem with the disk of a template (it was gone) 2.I tried to create a vm from this template 3.I got the error: Error while executing action: Cannot ${action} ${type}. VM doesn't exist Actual results: Error while executing action: Cannot ${action} ${type}. VM doesn't exist Expected results: formatted string Additional info:
Hi Nelli, Can you please describe a bit more what were the reproduce steps, like what was the problem with the Template's disk? and how can I reproduce it It seems that the message you got "Cannot ${action} ${type}. VM doesn't exist" is quite an old message (seems its origin is ACTION_TYPE_FAILED_VM_NOT_EXIST key) which was remove already at commit e432ac3d10dbb6d91fd764eb2ea15aee89181195. What seems odd to me because this commit was already merged last year and you were using vt16.6. If you can attach the engine and VDSM logs, I can make sure which key were used for the message, and if commit e432ac3d10dbb6d91fd764eb2ea15aee89181195 will solve this issue or not.
Hi Maor, I apologize but I dont have the logs as I assumed it will be easy to find this message in the code, but if you want to take a look at the environment, let me know (but you wont see the error as we removed this template already) as for reproducing, we got to a situation where a template existed, but its disk was removed from the storage, so when I tried to create a vm from this template, I got this error
(In reply to Nelly Credi from comment #2) > Hi Maor, > > I apologize but I dont have the logs as I assumed it will be easy to find > this message in the code, but if you want to take a look at the environment, > let me know (but you wont see the error as we removed this template already) Thanks I will check this, if this can be reproduced somehow that could be great. > > as for reproducing, we got to a situation where a template existed, but its > disk was removed from the storage, so when I tried to create a vm from this > template, I got this error
I didn't managed to reproduce this, and I can see that this message has been removed. Closing the bug for now, please re-open if you have explicit reproduce steps with the appropriate logs.
Hi Maor, Nelly, To reproduce this: 1) create a template 2) under /rhev/data-center/ locate the template's disk (image_id) 3) it will contain 3 files: <uuid>, <uuid>.meta, <uuid>.lease 4) remove only the data file: <uuid>
steps to reproduce in comment 5
(In reply to ratamir from comment #5) > Hi Maor, Nelly, > To reproduce this: > 1) create a template > 2) under /rhev/data-center/ locate the template's disk (image_id) > 3) it will contain 3 files: <uuid>, <uuid>.meta, <uuid>.lease > 4) remove only the data file: <uuid> I've done that, and all I got was an audit log error saying: "Volume does not exists" and "Failed to complete VM some_vm creation" Attaching the logs and a print screen
Created attachment 1064690 [details] engine
Created attachment 1064691 [details] audit log message
Nelly, Raz Can you please try to reproduce this in an oVirt 3.6 env, and if that does reproduce can u please attach the appropriate logs.
Talked with Raz, the issue of the uninitialized message does not seems to be an issue, closing this bug for now. If that re-produce please attach the appropriate logs and print screen.