cloudstack-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Sudhansu Sahu <sudhan...@gmail.com>
Subject Re: 4.5.1: VMsync issues with VRs?
Date Wed, 03 Jun 2015 09:42:34 GMT
In case of a out of band VM movement the VR will be rebooted to configure
the network rules. The solution was for 4.3 where we don't have Aggregate
command. In 4.5 we can use aggregate command to push the network rule.

You can raise a defect.

On Mon, Jun 1, 2015 at 8:27 PM, Rene Moser <mail@renemoser.net> wrote:

> Hi
>
> Before I file a bug, I would like to give some of you the chance to
> confirm an issue we faced during testing of 4.5.1.
>
> Environment:
>
> Hypervisor: VMware vsphere 5.1
> CloudStack: 4.5.1 (upstream)
> Networking: Advanced
> VR: systemvm-4.5 (shapeblue)
>
>
> Problem:
>
> We tested the VM sync which worked as expected for VMs.
>
> But after we migrated (computing only) a VR, the VR gets rebooted in
> every case and we see this in the logs:
>
>
> https://gist.githubusercontent.com/resmo/ce026c49373d54eb24e6/raw/1bf7d22c26fa07000cae5ab191e6a76d4b189fa7/gistfile1.txt
>
>
> Expected:
>
> VRs should not reboot after migration.
>
>
> This would be a blocker for us. Could anyone confirm this?
>
> Yours
> René
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message