I have tried to reproduce the bug using the most recent manila version. It does not occur, though. Actually, since the patch [1], the `netapp_root_volume_aggregate` is only set if it is different from False. So, the empty string is ignored, using the default ONTAP behavior.
However, the bug with that option may still occur with a different scenario.
1) `netapp_root_volume_aggregate` empty or not informed: it will use the default ONTAP behavior, which chooses the most appropriate aggregate to be the root. After the creation of vserver, the NetApp driver modifies the vserver for having access to the aggregates given by the set `netapp_aggregate_name_search_pattern`. In case the set does not contain the chosen aggregate, the share server setup will fail.
2) `netapp_root_volume_aggregate` invalid aggregate name: value is not part of the ONTAP aggregates, the share server setup will fail.
I have tried to reproduce the bug using the most recent manila version. It does not occur, though. Actually, since the patch [1], the `netapp_ root_volume_ aggregate` is only set if it is different from False. So, the empty string is ignored, using the default ONTAP behavior.
However, the bug with that option may still occur with a different scenario.
1) `netapp_ root_volume_ aggregate` empty or not informed: it will use the default ONTAP behavior, which chooses the most appropriate aggregate to be the root. After the creation of vserver, the NetApp driver modifies the vserver for having access to the aggregates given by the set `netapp_ aggregate_ name_search_ pattern` . In case the set does not contain the chosen aggregate, the share server setup will fail.
2) `netapp_ root_volume_ aggregate` invalid aggregate name: value is not part of the ONTAP aggregates, the share server setup will fail.
[1] https:/ /review. opendev. org/c/openstack /manila/ +/747048