<storage_connection
href="/api/storageconnections/91fca941-d9f3-496c-908f-92d31bce6a64"
id="91fca941-d9f3-496c-908f-92d31bce6a64"><address>
progress.brusselsairport.aero
</address><type>nfs</type><path>/media/ISO_DOMAIN</path></storage_connection>
??????
2014-06-25 6:54 GMT+02:00 Koen Vanoppen <vanoppen.koen(a)gmail.com>:
Ok, thanx.
Now when I try to remove the connection I get this:
[oVirt shell (connected(a)vega.brusselsairport.aero)]# remove
storageconnection 91fca941-d9f3-496c-908f-
92d31bce6a64
====================================================== ERROR
===================================================
status: 404
reason: Not Found
detail: Entity not found: null
================================================================================================================
2014-06-24 15:53 GMT+02:00 Dafna Ron <dron(a)redhat.com>:
> the destroy should clean the db only and any cleanup on the storage/hosts
> side should be done manually by the user.
>
> cleaning the iso domain from the vms would be a nice addition if not done
> today - can you please open a bug on this?
>
> Please check if your hosts have old mount to the iso side and umount it.
> restart of vdsm service on the hosts and engine service should clean any
> leftovers after that.
> if not, please file a bug since old connection should be clean from the
> db.
>
> Dafna
>
>
>
> On 06/24/2014 01:53 PM, Sven Kieske wrote:
>
>> well as far as I know you should put any domain
>> first into maintenance, then detach from all DCs
>> and then remove it.
>>
>> by force destroying you get what you now have:
>> old connections which are dead and log spam.
>>
>> So I assume it would be safe to delete the connection
>> to this storage domain, but ymmv.
>>
>> Am 24.06.2014 14:45, schrieb Koen Vanoppen:
>>
>>> By "destroying" it in ovirt management interface...
>>>
>>
>
> --
> Dafna Ron
>