You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi, i found out that if you have a FC group on the VNX already attached to your compute, New volumes will fail to attach to the VMs. This is because a host can only have one storage group associated with it in the VNX and Cinder is looking for (and will create) a group named the FQDN of the attaching compute. So, if you need to have non cinder LUNs attached to your compute you need to pre-create the storage group named the FQDN of your compute. When you do that cinder will see the group already created and associate new LUNs with it properly. It would be quite common for the compute to boot from FC in which case you need to create (or rename) that VNX storage group to make cinder work.
I hope this helps someone else who ran into same issue.
The text was updated successfully, but these errors were encountered:
Hi, i found out that if you have a FC group on the VNX already attached to your compute, New volumes will fail to attach to the VMs. This is because a host can only have one storage group associated with it in the VNX and Cinder is looking for (and will create) a group named the FQDN of the attaching compute. So, if you need to have non cinder LUNs attached to your compute you need to pre-create the storage group named the FQDN of your compute. When you do that cinder will see the group already created and associate new LUNs with it properly. It would be quite common for the compute to boot from FC in which case you need to create (or rename) that VNX storage group to make cinder work.
I hope this helps someone else who ran into same issue.
The text was updated successfully, but these errors were encountered: