thanks for the HEADsup, can you guys test 4.4.3 and confirm whether it
solves CLOUDSTACK-7399?
this kind off feedback is not spam but much appriciated and hereby solicited.
On Thu, Mar 26, 2015 at 1:33 PM, cs user wrote:
> Just to clarify, the fix was:
>
> update networks set broadcast_uri="vlan
Just to clarify, the fix was:
update networks set broadcast_uri="vlan://untagged" where mode='Dhcp';
As these were set to null.
Sorry for the spam!
On Thu, Mar 26, 2015 at 12:31 PM, cs user wrote:
> Hi Laurent,
>
> Many many thanks for this. We had the exact same problem but using
> xenserver
Hi Laurent,
Many many thanks for this. We had the exact same problem but using
xenserver as hosts. The fix for us was:
select name,broadcast_uri from networks where mode='Dhcp';
We were using basic networking as well.
We had upgraded from 4.3 to 4.4.2, using Xenserver 6.1.
Thank you!!!
On
Hi,
This mail to share a fight we had at INRIA upgrading our Cloudstack/KVM farm
from 4.2 to 4.4.2 following this documentation :
http://cloudstack-release-notes.readthedocs.org/en/latest/upgrade/upgrade-4.2.html
It's now solved, but I would like to share, as I think :
- it could helps other pe
