That sounds OK to me, the steps to add SF. That should create a datastore
per each created volume you create (if not mistaken). The other way is to
use SolidFireShared plugin, which should create a single datastore and
place all volumes in it (datastore=LUN=single SF volume).
Can you please answer
Hi Andrija,
> On 5. Sep 2019, at 15:07, Andrija Panic wrote:
> 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.solidfir
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 wrote:
> Christ
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
Hello,
Every time I restart management or reboot the machine, additional record is
added to mshost table. Sometime it happens that there multiple management
servers with same hostname showing as Up which I think causes confusion by
management server/agent. It's so odd.
Thanks for taking time to look into it.
https://pastebin.com/utPhEVkW
Regards
Christian
> On 5. Sep 2019, at 13:16, Andrija Panic 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, 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, 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 als
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
