[ovirt-users] All snapshots read only

[Colin Coe]

Hi and thanks for the response

1) RHEV v3.5.7
2) The VM was powered on and running fine when the snapshot was taken (this
is done through cron)
3) The snapshot was created via a Python oVirt SDK script
4) The status is showing "OK" for both the VM's disks and the snapshots
disks.

As a test, I took a snapshot of another VM that was running OK.  When the
snapshot was completed, the delete buttn was greyed out.

I turned the original server off and found that the snapshot button was no
longer greyed out.  When I turned the server back on, the delete button is
greyed out again.

My API script that creates the snapshots also deletes the snapshot from 7
days ago.  I see that the last successfully deleted was on Jan 26.  We
upgraded from v3.5.0 to v3.5.7 on Jan 24.  Nothing changed on the server
after Jan 24 so I'm a bit stumped.

Thanks

On Thu, Feb 4, 2016 at 5:46 PM, Raz Tamir <ratamir at redhat.com> wrote:

> Hi Colin,
> Can you share more info?
> 1) what version of oVirt you have?
> 2) what was the VM state when you tried to remove the snapshot?
> 3) How the snapshot was created in the first place (the VM state was UP or
> DOWN)?
> 4) What is the status of the snapshot's disks (click on snapshot tab and
> on the right hand side you have another 'disks' tab)?
>
>
>
>
>
> Thanks,
> Raz Tamir
> Red Hat Israel
>
> On Thu, Feb 4, 2016 at 8:44 AM, Colin Coe <colin.coe at gmail.com> wrote:
>
>> Hi all
>>
>> I've just noticed that all VM snapshots on one of our prod RHEV setups
>> have gone read-only (i.e. delete is greyed out).
>>
>> Has anyone else seen this?
>>
>> Is there an easy fix for this?  We have a bunch of VVMs being snapshotted
>> nightly with snapshots being deleted after 7 days.
>>
>> Thanks
>>
>> CC
>>
>> _______________________________________________
>> Users mailing list
>> Users at ovirt.org
>> http://lists.ovirt.org/mailman/listinfo/users
>>
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ovirt.org/pipermail/users/attachments/20160205/b100a198/attachment-0001.html>