Hello Guys,
We are evaluating oVirt , and this morning I had to face to a side effect ( small impact because oVIrt Datacenter is actually a small one).
- I added a new Storage domain from iSCSI SAN
- Not all hosts HBA were authorized to access to this LUN (lack of configuration on SAN side)
- One of ovirt Node on four nodes into my datacenter couldn’t access to the LUN => this ovirt node has gone into “Non-responsible” state. => All VMs running into this host has gone to another
My question is regarding the “operational mode” :
- If I add a Storage Domain which is not already fully configured / badly configured (“regarding HBA acces granted on SAN side), when I add the Storage Domain to my DC, each oVirt node into my datacenter will move to “non-operationnal” state after fews seconds since no one will be able to log into the new LUN ? (This state change can have some “major effect” (vm migration between hosts without any logic) ?)
Does I miss something ?
Is there a guard ? Is Cluster Fencing policy option: Skip fencing on cluster connectivity issues => Threshold: xx% can protect this type of error ?
Regards,
Jean-Baptiste