So it seems in both 3.8 and 4.0 of Provisioning Manager it will not create an iGroup on both filers in a cluster. We run active/active, and when we provision storage even with the policy checked for "storage controler failure" the policy will only create and map the iGroup on the system that holds the storage. Is this a known bug, or am I doing something wrong?
The igroup will only be created on the controller, where you provision the storage. You don't need the same igroup on both controllers since in case of a cluster failover the igroup will be present in the virtual instance of the controller which had the problem. Only if you present storage from both controllers to the same host, you have to have an igroup on both controllers.