The complete details for that bug are not yet online. However I assure you that the footprint you have observed is that bug. The crashing will be fixed via a code change in an upcoming UM release.
The duplicate aggr situation could happen after disks are inserted into a controller that contain partial data from a previous aggr, and that which now show as a partial or complete aggr with a name that duplicates another in the controller.
You might check "aggr status -r" and ensure there are no incomplete or duplicate aggr names on the controller you referenced.
Additionally, are you using the VMware NetApp Storage Adapter in your environment?