On Wed, Apr 17, 2013 at 03:25:47PM -0500, Jeronimo Garcia wrote: > I guess this won't be solved in 4.1 either: >
Can you file a bug for this please? > > > On Wed, Apr 17, 2013 at 11:41 AM, Jeronimo Garcia <garciaj...@gmail.com>wrote: > > > Hi List. > > > > I've experienced some erratic behavior when when setting a host in > > maintenance mode: > > > > I had about 6 Virtual routers running and 2 system vms in a given host , > > after putting this host in maintenance mode the system vms failed > > over successfully. > > > > The problem came in when the VirtualRouters failed over , they did not > > start up at all, even after waiting 1 hour for HA to kick in . > > > > When i went on and start the virtual routers manually it would fail with > > this error: > > > > *2013-04-17 08:54:39,566 DEBUG [allocator.impl.FirstFitAllocator] > > (catalina-exec-2:null) Host name: kickseed, hostId: 1 is in avoid set, > > skipping this and trying other available hosts* > > *2013-04-17 08:54:39,566 DEBUG [allocator.impl.FirstFitAllocator] > > (catalina-exec-2:null) Host Allocator returning 0 suitable hosts* > > * > > * > > The work around i found is : > > > > > > - Destroying the virtual router for network X > > - Restart network X > > > > Is this the expected behaviour for virtual router fail over ? > > I'm using cloudstack 4.0.1 on Ubuntu . > > > > Thanks! > > > > > >
