Andrija,
You were right! The isolation_uri and the broadcast_uri where both blank for
the problem VMs. Once I corrected the issue, I was able to migrate them inside
of CS without issue. Thanks for helping me get to the root cause of this
issue.
Thanks,
David Mabry
On 2/1/18, 3:27 PM, "D
Hi all,
I will be at Fosdem in Brussels this weekend, and I know Daan is going to be
there too - if you're going it would be lovely to meet you and discuss
CloudStack among other things, tweet me @rhtyd.
Cheers.
rohit.ya...@shapeblue.com
www.shapeblue.com
53 Chandos Place, Covent Garden, Lond
Andrija,
Thanks for the tip. I'll check that out and let you know what I find.
Thanks,
David Mabry
On 2/1/18, 2:04 PM, "Andrija Panic" wrote:
The customer with serial number here :)
So, another issue which I noticed, when you have KVM host disconnections
(agent disconnect), t
The customer with serial number here :)
So, another issue which I noticed, when you have KVM host disconnections
(agent disconnect), then in some cases in the cloud.NICs table, there will
be missing broadcast URI, isolatio_URI and state or similar filed that is
NULL instead of having correct value
Hi Everyone,
I’m cross-posting again…
I think that it would be great if we could have a couple of CloudStack
presentations, but maybe we could pool a user’s story with development piece to
showcase CloudStack from both perspectives.
Any one up for this?
paul.an...@shapeblue.com
www.shapeblu
People,
I went ahead and added some projects with label gsoc2018 to ur issues list.
I'm sure all of you can do way better then me ;)
https://issues.apache.org/jira/issues/?jql=project%20%3D%20CLOUDSTACK%20AND%20labels%20%3D%20gsoc2018
regards,
--
Daan
