Forced deletion of objects/entries (--force option)
Hi All,
Yesterday I setup a new OVM 3.0.2 environment; 1 system with Mgr, 3 systems with OVM Server, 2 (OpenFiler) fileservers doing NFS and iSCSI. Created new pool, attached NFS for heartbeat and cluster etc. Created repository, decided to go for iSCSI instead.. That's where the problems started:
- Tried to remove 3 servers from the pool, it failed with the last server
- Last server was not visible anymore (no hardware visible in Mgr, could not discover again, no unassigned systems)
- Pool could not be deleted because there were servers still registered (but not visible in my GUI)
- Repository could not be deleted because repository was still linked to servers
- Repository could not be un-presented to all systems because there were no systems with the repo mounted
- Could not delete pool because servers existed
- etc.etc.etc.
Basically, I spend 3 hours doing everything I could think off and the only result was this loop of 'Failed' or 'Aborted' jobs. I simply wanted to rm -rf <repository> <serverpool>..
Question: Is there something like a forced removal even if some dependencies still exist ?
I finally ended up clearing and writing a new repository and scratching (deleting /etc/ovs-agent/db/server) the servers. If this would happen in a production environment managing 40+ systems, I would be 'a bit annoyed'..
Thanks for any response !
Regards, Robert