Description of problem: I changed NFS settings on an external NFS server / storage domain (so that only LAN ips could connect) - afterwards it was locked and remained locked in ovirt. I disabled all hosts and turned off (powered off) the storage NFS server and it still remained locked. I couldn't even 'force remove' the data center as you needed to disable storage - I couldn't as it was locked.... Version-Release number of selected component (if applicable): ---------------------------------------- [root@frontend ~]# rpm -qa | grep ovirt ovirt-engine-jbossas-1.2-2.fc16.x86_64 ovirt-engine-log-collector-3.0.0_0001-1.6.fc16.x86_64 ovirt-engine-webadmin-portal-3.0.0_0001-1.6.fc16.x86_64 ovirt-engine-dbscripts-3.0.0_0001-1.6.fc16.x86_64 ovirt-engine-iso-uploader-3.0.0_0001-1.6.fc16.x86_64 ovirt-engine-setup-3.0.0_0001-1.6.fc16.x86_64 ovirt-engine-config-3.0.0_0001-1.6.fc16.x86_64 ovirt-engine-tools-common-3.0.0_0001-1.6.fc16.x86_64 ovirt-engine-restapi-3.0.0_0001-1.6.fc16.x86_64 ovirt-engine-backend-3.0.0_0001-1.6.fc16.x86_64 ovirt-engine-genericapi-3.0.0_0001-1.6.fc16.x86_64 ovirt-engine-jboss-deps-3.0.0_0001-1.6.fc16.x86_64 ovirt-engine-userportal-3.0.0_0001-1.6.fc16.x86_64 ovirt-engine-notification-service-3.0.0_0001-1.6.fc16.x86_64 ovirt-engine-3.0.0_0001-1.6.fc16.x86_64 ---------------------------------------- How reproducible: Not sure - I hope to never see the issue again. Steps to Reproduce: 1. edit nfs sertting 2. see nfs isn't working in ovirt - try to enable 3. storage is now locked and can be removed Actual results: Not able to detach, remove storage Expected results: storage works... Additional info: I thought i would send this - I was asked to by an Ovirt developer in IRC . Also it is an example of being trapped in a catch22 situation - i.e not being able to remove storage due to it being locked. atatched log.
Created attachment 566575 [details] log
I resoved it by edited the DB UPDATE storage_pool_iso_map SET status='6' where storage_id='5fa9fa59-ba8d-4825-96ec-130275dcd004'; then I could remove it.
Closing old bugs. If this issue is still relevant/important in current version, please re-open the bug.