12:03 p.m.
I'm noticing this on 4.3.8 and I don't have understood exactly the raising
condition, if UI based or what
At first I thought it was the bootable flag, but it is not, apparently
vm1 powered on with two disks
I select the VM then Disks subtab
select line of second disk --> edit --> OK
All goes well
Then, remaining in the same Disks subtab window I select the line of the
first disk --> Edit --> OK
And now I get the error window:
"
Error while executing action:
vm1:
- Cannot edit Virtual Disk. At least one of the VMs is not down.
"
?
Then I go and select another powered on VM, vm2, with only one disk, the
one with bootable flag, and I'm able to edit it successfully.
Then I come back and select vm1 and Disks subtab, select again the first
line of the boot disk --> Edit --> OK
and I'm able to edit with success..... but eg if I want to modify both
alias and description fields I have to do one at a time, otherwise if in
the same window I try to modify both and then press OK I still get the
error message above.
Can anyone verify/test? I was able to reproduce on bot oVirt 4.3.8 and RHV
4.3.8
Gianluca
12:39 p.m.
Hi Gianluca,
I'm working on master 4.4 and I didn't run into this one.
Was the second disk shareable?
In the case of editing a shareable disk, you first need to shut down all
the VMs that disk attached to.
Also, editing the VM attached disks should accrue one by one, as you can't
edit them both at once (the edit button should be grayed out).
For a deeper look, can you please attach screenshots and UI+engine logs?
*Regards,*
*Shani Leviim*
On Thu, Mar 12, 2020 at 11:06 AM Gianluca Cecchi <gianluca.cecchi(a)gmail.com>
wrote:
I'm noticing this on 4.3.8 and I don't have understood
exactly the raising
condition, if UI based or what
At first I thought it was the bootable flag, but it is not, apparently
vm1 powered on with two disks
I select the VM then Disks subtab
select line of second disk --> edit --> OK
All goes well
Then, remaining in the same Disks subtab window I select the line of the
first disk --> Edit --> OK
And now I get the error window:
"
Error while executing action:
vm1:
- Cannot edit Virtual Disk. At least one of the VMs is not down.
"
?
Then I go and select another powered on VM, vm2, with only one disk, the
one with bootable flag, and I'm able to edit it successfully.
Then I come back and select vm1 and Disks subtab, select again the first
line of the boot disk --> Edit --> OK
and I'm able to edit with success..... but eg if I want to modify both
alias and description fields I have to do one at a time, otherwise if in
the same window I try to modify both and then press OK I still get the
error message above.
Can anyone verify/test? I was able to reproduce on bot oVirt 4.3.8 and RHV
4.3.8
Gianluca
_______________________________________________
Users mailing list -- users(a)ovirt.org
To unsubscribe send an email to users-leave(a)ovirt.org
Privacy Statement: https://www.ovirt.org/privacy-policy.html
oVirt Code of Conduct:
https://www.ovirt.org/community/about/community-guidelines/
List Archives:
https://lists.ovirt.org/archives/list/users@ovirt.org/message/T42ESMTAWPV...
5:14 p.m.
On Thu, Mar 12, 2020 at 10:40 AM Shani Leviim <sleviim(a)redhat.com> wrote:
No, both first disk and second disk dedicated to that VM
In the case of editing a shareable disk, you first need to shut down all
> the VMs that disk attached to.
> Also, editing the VM attached disks should accrue one by
one, as you can't
> edit them both at once (the edit button should
be grayed out).
Yes, sure. I select the line of one disk and then "Edit" button
> 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
Hi Gianluca,
I'm working on master 4.4 and I didn't run into this one.
well
Was the second disk shareable?
5:31 p.m.
On Thu, Mar 12, 2020 at 3:14 PM Gianluca Cecchi <gianluca.cecchi(a)gmail.com>
wrote:
On Thu, Mar 12, 2020 at 10:40 AM Shani Leviim
<sleviim(a)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?us...
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
5:45 p.m.
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(a)gmail.com>
wrote:
On Thu, Mar 12, 2020 at 3:14 PM Gianluca Cecchi
<gianluca.cecchi(a)gmail.com>
wrote:
> On Thu, Mar 12, 2020 at 10:40 AM Shani Leviim <sleviim(a)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?us...
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
1713
days inactive
1716
days old
4 comments
2 participants
participants (2)
-
Gianluca Cecchi -
Shani Leviim