<html><body><div style="font-family: times new roman, new york, times, serif; font-size: 12pt; color: #000000"><div><br>Hi !<br></div><div><br></div><div>I finally solved my problem by removing information related to broken storage in the engine database.<br></div><div><br></div><div>I post below the sql queries I executed in postgres (with engine stopped while executing them) in order to remove storage domain. Maybe it can be useful for somebody else in the same situation.<br></div><div><br></div><div><br>Connect to database<br></div><div><br></div><div># su - postgres<br># psql engine<br></div><div><br></div><div><br>identify broken storage <br></div><div><br></div><div>engine=# select id, storage_name from storage_domain_static;<br> id | storage_name <br>--------------------------------------+------------------------<br> 34c95a44-db7f-4d0f-ba13-5f06a7feefe7 | my-broken-storage-domain<br></div><div><br></div><div><br></div><div><br></div><div>identify ovf disks on this storage<br></div><div><br></div><div>engine=# select storage_domain_id, ovf_disk_id from storage_domains_ovf_info where storage_domain_id = '34c95a44-db7f-4d0f-ba13-5f06a7feefe7';<br> storage_domain_id | ovf_disk_id <br>--------------------------------------+--------------------------------------<br> 34c95a44-db7f-4d0f-ba13-5f06a7feefe7 | 033f8fba-5145-47e8-b3b5-32a34a39ad11<br> 34c95a44-db7f-4d0f-ba13-5f06a7feefe7 | 2d9a6a40-1dd0-4180-b7c7-3829a443c825<br></div><div><br></div><div><br>engine=# delete from storage_domain_dynamic where id = '34c95a44-db7f-4d0f-ba13-5f06a7feefe7';<br>engine=# delete from storage_domain_static where id = '34c95a44-db7f-4d0f-ba13-5f06a7feefe7';<br>engine=# delete from base_disks where disk_id = '033f8fba-5145-47e8-b3b5-32a34a39ad11';<br>engine=# delete from base_disks where disk_id = '2d9a6a40-1dd0-4180-b7c7-3829a443c825';<br>engine=# delete from storage_domains_ovf_info where storage_domain_id = '34c95a44-db7f-4d0f-ba13-5f06a7feefe7';<br>engine=# delete from storage_pool_iso_map where storage_id = '34c95a44-db7f-4d0f-ba13-5f06a7feefe7';<br></div><div><br></div><div><br>identify and delete luns and connections related to storage (i did not take notes of results of these ones, but it was easy to find the good lines). Also, i noticed that lun_storage_server_connection_map only contained information about iscsi storage, not fiber channel.<br></div><div><br></div><div>engine=# select * from luns;<br></div><div><br></div><div>engine=# delete from luns where physical_volume_id = 'IqOdm6-BWuT-9YBW-uvM1-q41E-a3Cz-zPnWHq';<br>engine=# delete from lun_storage_server_connection_map where storage_server_connection='1b9f3167-3236-431e-93c2-ab5ee18eba04';<br>engine=# delete from lun_storage_server_connection_map where storage_server_connection='ea5971f8-e1a0-42e3-826d-b95e9031ce53';<br>engine=# delete from storage_server_connections where id='1b9f3167-3236-431e-93c2-ab5ee18eba04';<br>engine=# delete from storage_server_connections where id='ea5971f8-e1a0-42e3-826d-b95e9031ce53';<br></div><div><br></div><div><br>delete remaining disk(s) ; I had 1 virtual disk on this storage<br></div><div><br></div><div>engine=# delete from base_disks where disk_id='03d651eb-14a9-4dca-8c87-605f101a5e0c';<br>engine=# delete from permissions where object_id='03d651eb-14a9-4dca-8c87-605f101a5e0c';<br></div><div><br></div><div><br>Then started engine and all is fine now.<br></div><div><br></div><div><br></div><div><br></div><div>----- Mail original -----<br>> De: "Amit Aviram" <aaviram@redhat.com><br>> À: "Olivier Navas" <olivier.navas@sdis33.fr><br>> Envoyé: Mardi 6 Janvier 2015 17:24:19<br>> Objet: Re: [ovirt-users] Can't remove a storage domain related to a broken hardware<br>> <br>> <br>> <br>> ----- Original Message -----<br>> From: "Olivier Navas" <olivier.navas@sdis33.fr><br>> Hi, can you please add the engine log?<br>> <br>> To: users@ovirt.org<br>> Sent: Tuesday, January 6, 2015 11:28:42 AM<br>> Subject: [ovirt-users] Can't remove a storage domain related to a broken<br>> hardware<br>> <br>> <br>> Hello Ovirt users !<br>> <br>> I experienced an hardware failure on a ISCSI storage making it unrecoverable,<br>> and I would like to remove it from storage domains.<br>> <br>> There was 1 disk on this storage domain, and this disk isn't attached to any<br>> VM anymore, but I still can't detach this storage domain from cluster.<br>> <br>> The storage domain is in "inactive" status and if I try to "detach" it from<br>> data center, ovirt tries to activate it. Obviously it can't activate it<br>> since hardware is broken, and it fails after several minutes with the event<br>> "Failed to detach Storage Domain my_storage_domain to Data Center Default.<br>> (User: admin)". I can post my engine.log if useful.<br>> <br>> I need a way to force removal of this storage domain. Any trick would be<br>> greatly appreciated.<br>> <br>> Perhaps does Ovirt miss some sort of "force detach, i know what i'm doing"<br>> button ?<br>> <br>> I am running an Ovirt 3.5 cluster (engine with CentOS 6.6, 4 nodes with<br>> CentOS 7) with FC and ISCSI storage domains.<br>> <br>> Thanks for your help.<br>> <br>> <br>> <br>> <br>> Ce courriel et tous les fichiers attachés qu'il contient sont confidentiels<br>> et destinés exclusivement à la personne à laquelle ils sont adressés. Si<br>> vous avez reçu ce courriel par erreur, merci de le retourner à son<br>> expéditeur et de le détruire. Il est rappelé que tout message électronique<br>> est susceptible d'alteration au cours de son acheminement sur internet.<br>> Seuls les documents officiels du SDIS sont de nature à engager sa<br>> responsabilité. Les idées ou opinions présentées dans ce courriel sont<br>> celles de son auteur et ne représentent pas nécessairement celles du SDIS de<br>> la Gironde.<br>> <br>> _______________________________________________<br>> Users mailing list<br>> Users@ovirt.org<br>> http://lists.ovirt.org/mailman/listinfo/users<br>> <br></div></div>
<br>
<hr><font size="-2"><em>
Ce courriel et tous les fichiers attachés qu'il contient sont confidentiels et destinés exclusivement à la personne à laquelle ils sont adressés. Si vous avez reçu ce courriel par erreur, merci de le retourner à son expéditeur et de le détruire. Il est rappelé que tout message électronique est susceptible d'alteration au cours de son acheminement sur internet. Seuls les documents officiels du SDIS sont de nature à engager sa responsabilité. Les idées ou opinions présentées dans ce courriel sont celles de son auteur et ne représentent pas nécessairement celles du SDIS de la Gironde.
</font></em>
<br></body></html>