Actually, what I wanted to check also - in this error message is mentioned "root-29" which is the root volume of the VM with ID 29 - can you confirm that is YOUR VM which failed to start, or is this perhaps some leftover volume/datastore
On Thu, 5 Sep 2019 at 15:07, Andrija Panic <andrija.pa...@gmail.com> wrote: > Christian, > > the message is that no host is connected to that specific datastore - > "Unable to start VM on Host[-1-Routing] due to StartCommand failed due to > Exception: java.lang.RuntimeException > Message: Datastore '-iqn.2010-01.com.solidfire:x64j.root-29.17-0' is not > accessible. ***No connected and accessible host is attached to this > datastore***." > > You can see that message being returned by VMware actually, not ACS (I > checked the code for that message - no results) > > https://vmninja.wordpress.com/2019/04/05/remove-inaccessible-datastore-from-inventory/ > > > Can you describe exactly how did you add SF to the ACS/VMware - you > already wrote you created iSCSI HBAs....? What are the parameters/options > used to add SF as Primary Storage to ACS? I expect (since no proper > documentation yet) that you might have somehow incomplete or wrong setup in > place. > > Andrija > > On Thu, 5 Sep 2019 at 13:29, <christian.kir...@zv.fraunhofer.de> wrote: > >> Thanks for taking time to look into it. >> >> https://pastebin.com/utPhEVkW >> >> Regards >> Christian >> > On 5. Sep 2019, at 13:16, Andrija Panic <andrija.pa...@gmail.com> >> wrote: >> > >> > Can you share the mgmt logs when the problem happens? Please upload to >> > pastebin or similar. >> > >> > Andrija >> > >> > On Thu, 5 Sep 2019 at 11:45, <christian.kir...@zv.fraunhofer.de> wrote: >> > >> >> Hi, >> >> >> >> I have managed to overcome the problem by forcing Cloudstack to >> reconnect >> >> the host after I configured the iSCSI HBA. >> >> It seems that Cloudstack also scans for such capabilities during the >> >> reconnect. >> >> >> >> But now I have trouble deploying VMs on the storage, sometimes it is >> >> successful and sometimes not, I was not able to find a pattern. >> >> If the deployment fails Cloudstack says that the IQN was not reachable >> by >> >> the host, the odd part is that there is no such message in vcenter so >> it >> >> seems there was no attempt to attach the storage to the ESXi… >> >> >> >> Does anyone know this kind of issue? >> >> >> >> Regards >> >> Christian >> >> >> >> >> >> On 2019/09/04 14:13:36, <c...@zv.fraunhofer.de> wrote: >> >>> Hi,> >> >>> >> >>> >> >>> >> >>> we are currently doing a PoC with SolidFire and CloudStack and trying >> to >> >> figure out if it’s a fitting solution for our use cases.> >> >>> >> >>> >> >>> >> >>> But I am stuck at the point when CloudStack tries to create a VM on >> the >> >> solid fire storage.> >> >>> >> >>> I can see that it has already copied the template to a SolidFire >> Volume >> >> but then the error message "Not all hosts in the compute cluster >> support >> >> iSCSI.” appears in the logs.> >> >>> >> >>> >> >>> >> >>> On the ESXi I have created a iSCSI HBA and attached it to a VMKernel >> >> adapter, is there anything else to do?> >> >>> >> >>> Is there any documentation for the setup?> >> >>> >> >>> I have only found the youtube videos by Mike, but they does not focus >> on >> >> the vsphere setup part.> >> >>> >> >>> >> >>> >> >>> Regards> >> >>> >> >>> Christian> >> >> >> >> >> >> -- >> >> Christian Kirmse >> >> Fraunhofer-Gesellschaft e.V. / Zentrale >> >> Abteilung C7 Kommunikationsmanagement >> >> Schloss Birlinghoven, 53754 Sankt Augustin >> >> Tel: (+49 2241) 14-2719 >> >> Fax: (+49 2241) 144-2719 >> >> mailto:christian.kir...@zv.fraunhofer.de >> >> http://www.fraunhofer.de >> >> >> >> >> > >> > -- >> > >> > Andrija Panić >> >> > > -- > > Andrija Panić > -- Andrija Panić
