[Users] python SDK remove VM once the storage is formatted/detached.

[karthik S]

In short, I am looking for  "Destroy VM" (along with destroy Disks) similar
to "Destroy Storage Domain"

-Karthik


On Sun, Jan 5, 2014 at 1:55 PM, karthik S <karthik.lubdup at gmail.com> wrote:

> When the storage is formatted, the storage Domain gets down status.
>
> From UI, when I tried to deactivate the storage domain from the
> datacenter, I was asked to remove all the removes first. I could not remove
> the VM because the storage domain is in down state. I could not remove the
> storage domain (System >> storage domain>> "Remove" ) too. The remove
> option remained disabled.
>
> I could only "destory" the storage domain. The storage domain was
> destroyed, but the vm which were in "Not Responding" status are still seen.
> The destory storaged domain did not destory the vms.
>
> All the above were done using UI. Not sure using ovirtsdk would have made
> any diffrence.
>
> Now the only option I have is to remove the stale vms  ("?" vms) by
> getting into database.
>
> May be an option in the UI to "remove VM from inventory/database" (and
> also ovirtsdk implemention of it).
> If there is no existing solution, I can file a bug/ RFE ?
>
> -Karthik
>
>
>
>
>
> On Sun, Jan 5, 2014 at 10:52 AM, Itamar Heim <iheim at redhat.com> wrote:
>
>> On 01/04/2014 10:50 PM, karthik S wrote:
>>
>>>
>>> Is there a way to remove VMs entries from rhev manager using python
>>> ovirt-sdk "once the storage becomes unavailble" . - Something equivalent
>>> to "Remove from Inventory" in Vmware vsphere. ?
>>>
>>> Currently I get into the postgres db and delete the entries, manually.
>>>
>>
>> did you try removing the missing storage domain from the system?
>>
>>
>>> -Karthik
>>>
>>>
>>>
>>>
>>>
>>> _______________________________________________
>>> 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/20140105/9faebd30/attachment-0001.html>