
Other links
CloudPlatform 4.x
Cannot add VMFS datastore as primary storage
First, myself and my shop are new to clouplatform, so please bear with me. We are however very experienced with VMware\ESXi. I have a new cloudplatform environment being setup. The hypervisors are VMware ESXi 5.1, and vCenter 5.1. During initial configuration, I selected advanced network deployment. Running through the initial setup, all resources add successfully until we get to primary storage. When attempting to add the Primary storage, an alert is immediately generated under general alerts on the dashboard stating "Host - Unable to attach storage poolxx to host1 (Timestamp)". This error repeats each time the procedure is attempted. The pool number increments up each time an attempt is made. The management server lives on the same management vlan as the ESXi hosts. The management server also has confirmed access to vCenter on 443. This is not a vCenter permissions issue as we have tested this using full vCenter privs as well. I have been working with Citrix support for well over a month on something I believe is probably a very simple issue. Anyone have any ideas? I would be happy to supply more information upon request. Thanks in advance!
Previous 5 comments



James, I see that this was resolved by working with Citrix Support.

Indeed. Once engineering got involved the problem was quickly diagnosed. The issue stemmed from spaces in the datacenter name within vSphere. Once the spaces were removed, and all resources removed and re-created, all was well. We are currently working through an NFS issue dealing with in house policies preventing NFS from working the way it is designed to work with CloudPlatform. I don't want to complain here, but this issue could have been resolved much faster. Getting past level 1 support always takes longer than it should really take. In my opinion if a support request has no progress after a week at most it should be escalated. Here's hoping for a more streamlined process with future requests. Thanks to all that helped, and I am appreciative. Just frustrated at how long it took. Thanks!


James, I am not sure why you have trouble in replying to this post but you could get it sorted by reporting it to the site administrator by clicking on "Give us feedback".
For the benifit of others I will paste the resolution that you said worked for you:
Indeed. Once engineering got involved the problem was quickly diagnosed. The issue stemmed from spaces in the datacenter name within vSphere. Once the spaces were removed, and all resources removed and re-created, all was well. We are currently working through an NFS issue dealing with in house policies preventing NFS from working the way it is designed to work with CloudPlatform.
Participate
Ask, Discuss, Answer
