Hi All,
Sorry didn't particpate discussion. Got pretty big issue with the cloud
yesterday. Very intersting one.
I have 2 networks with 2 dedicated VR (not VPC). One of the netowork with
default gateway, the second one just for internal interconnect between VMs.
Both network are
Donnerstag, 28. Januar 2016 17:20
>An: users@cloudstack.apache.org
>Betreff: Re: AW: AW: AW: upgrading 4.5.2 -> 4.6.0 virtualrouter upgrade timeout
>
>The 4.7.1 packages will be there soon. I’d advise anyone currently on 4.6 to
>upgrade to it as it has several speed improvements.
&
Hi!
To follow up:
- I upgraded to 4.7.0 (there are no 4.7.1 el6 RPMs yet, neither from CloudStack
nor from Shapeblue)
- The problem still persists
- It seems that VRs can be created on XenServer, but not on KVM. I tried
forcing new VRs to XenServers only via host tags, but the decision to use
Hi Martin,
4.7.1 has a fix for the overall timeout of 120 seconds. I expect the packages
will be ready in a day or two.
If XenServer works, try setting system.vm.default.hypervisor to XenServer and
it will not use another hypervisor.
Regards,
Remi
On 28/01/16 13:38, "Martin Emrich"
-Ursprüngliche Nachricht-
Von: Remi Bergsma [mailto:rberg...@schubergphilis.com]
Gesendet: Donnerstag, 28. Januar 2016 14:09
An: users@cloudstack.apache.org
Betreff: Re: AW: AW: upgrading 4.5.2 -> 4.6.0 virtualrouter upgrade timeout
Hi Martin,
4.7.1 has a fix for the overall timeout of
: AW: upgrading 4.5.2 -> 4.6.0 virtualrouter upgrade timeout
The 4.7.1 packages will be there soon. I’d advise anyone currently on 4.6 to
upgrade to it as it has several speed improvements.
What version was this Martin?
Regards,
Remi
On 28/01/16 15:46, "Martin Emrich" <martin.em
4.7.1 also affected.
All versions use 4.6 templates.
P.S.: would it be usefull to move discussion to devs list. Looks like it's
pretty big issue.
Hi!
After upgrading from 4.5.2 to 4.6.2, I also face this issue. We use both
KVM and XenServer. Any stable workaround for this?
Thanx
Martin
The routers from Daniel work when we bumped global setting
router.aggregation.command.each.timeout to 20 or higher. You may need to
upgrade to 4.7.1 for that to work, but that's a good thing to do anyway because
it has a load of fixes over 4.6. The upgrade is quick and painless.
For the
Hi!
After upgrading from 4.5.2 to 4.6.2, I also face this issue. We use both KVM
and XenServer. Any stable workaround for this?
Thanx
Martin
-Ursprüngliche Nachricht-
Von: Andrei Mikhailovsky [mailto:and...@arhont.com]
Gesendet: Freitag, 18. Dezember 2015 02:55
An: users
