Are there any VDSM/server logs as well?
It's hard to tell, as it's not reproducing.

IMHO, the VM was locked before the failed try, and since it's status wasn't 'DOWN' the message came up.

Regards,
Shani Leviim


On Thu, Mar 12, 2020 at 4:31 PM Gianluca Cecchi <gianluca.cecchi@gmail.com> wrote:
On Thu, Mar 12, 2020 at 3:14 PM Gianluca Cecchi <gianluca.cecchi@gmail.com> wrote:
On Thu, Mar 12, 2020 at 10:40 AM Shani Leviim <sleviim@redhat.com> wrote:



For a deeper look, can you please attach screenshots and UI+engine logs?

Regards,
Shani Leviim



I was trying to reproduce now in similar ways not able to create the problem.... I will search for logs

Gianluca


you see in extract of engine.log here:
https://drive.google.com/file/d/1vDY64QaRkb8LWHJ9gD16bsJlyovISNwr/view?usp=sharing

first step of editing the second disk "c8_Disk2" of VM c8 with success at 2020-03-12 09:51:28,680+01

error (WARN line) related to attempt of editing the boot disk named "c8_boot" of the same VM at 2020-03-12 09:51:40,359+01 with reason:
Validation of action 'UpdateVmDisk' failed for user tekka@my_domain@my_domain. Reasons: VAR__ACTION__UPDATE,VAR__TYPE__DISK,ACTION_TYPE_FAILED_VM_IS_NOT_DOWN

second attempt (after doing similar actions on disks of another VM named c8client) that had success for the same disk "c8_boot" of VM c8 at 2020-03-12 09:52:15,928+01

Gianluca