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
I am trying to create a storage pool using terraform. Despite providing the shared vpc host project number, it still tries to look for the network in the service project and gives an error.
` # module.cloud_volumes.netapp-gcp_storage_pool.regional-storage-pool will be created
│ Error: Error when creating - VPC peering network for TenancyUnit 'projects/642414531654/global/networks/prd-si-network' not found. Use the correct vpc name and ensure VPC network peering with tenant project has already been established.
There are no issues when trying to create the pool manually and the private service peering is already set up. I also tried to import the manually created pool into terraform, but looks like that feature isn't implemented yet.
The text was updated successfully, but these errors were encountered:
I looked in the code and looks pools are missing handling of shared_vpc_project_number.
For volume, we read shared_vpc_project_number in resourceGCPVolumeCreate
I don't see us doing that in resourceGCPStoragePoolCreate
I am trying to create a storage pool using terraform. Despite providing the shared vpc host project number, it still tries to look for the network in the service project and gives an error.
` # module.cloud_volumes.netapp-gcp_storage_pool.regional-storage-pool will be created
}
`
│ Error: Error when creating - VPC peering network for TenancyUnit 'projects/642414531654/global/networks/prd-si-network' not found. Use the correct vpc name and ensure VPC network peering with tenant project has already been established.
There are no issues when trying to create the pool manually and the private service peering is already set up. I also tried to import the manually created pool into terraform, but looks like that feature isn't implemented yet.
The text was updated successfully, but these errors were encountered: