UNSOLVED

beornwulf

updated

10 years ago

B

beornwulf

1 Rookie

9 Posts

0

1415

December 14th, 2016 12:00

Inventory error attempting to deploy isilon sd cluster

Hello, I am attempting to deploy an isilon sd cluster to a vcenter 6 (appliance) environment. I have all of the prerequisites covered however I am getting an error when i select the option to Create IsilonSD Cluster option. I am able to see the screen to select number of nodes, data disks, etc,  but upon clicking next I receive the following error :

"Error: Query Inventory Details: Cannot retrieve "mydatacentername" datacenter inventory details"

I know the query to vcenter is able to check inventory properly as I removed the nodes from vcenter and tried again to see if it would show a different error and it did show an error that stated there were not enough hosts required to proceed........

Any suggestions would be great, tks

Jeremy

  • sak99

    34 Posts

    814

    0

    Posted June 13th, 2017 12:00

    Can you retry using the latest release: IsilonSD Edge Management  Server 1.0.2 with OneFS version 8.1 ?


    Thanks

  • 814

    0

    Posted January 24th, 2018 13:00

    Hi Jeremy

    I am experiencing the same issue. How did you resolve this issue.

    Thanks,

    Denise

  • sak99

    34 Posts

    814

    0

    Posted January 24th, 2018 14:00

    Hi Denise,

    Which management server version are you using ? Are you using linked vCenter setup ?

    If yes, there is a new 1.0.3 version released recently with linked vCenter support.


    Thanks.

  • 814

    0

    Posted January 24th, 2018 14:00

    Yes I am using version 1.0.3. I can see the plugin registered in the vSphere Web Client.

    I am trying to setup a very simple setup - one ESXI host.

  • sak99

    34 Posts

    814

    0

    Posted January 24th, 2018 14:00

    Can you post the logs & if possible screenshot of error message ?

    You can find logs at /usr/share/virtmgmt/logs/isilonsd.log

  • 814

    0

    Posted February 1st, 2018 06:00

    I realised it was an issue with my datastore not being large enough.