On Tue, May 07, 2013 at 03:18:03PM +0000, Kishan Kavala wrote:
> Chip,
>  I'll look into CLOUDSTACK-2309. Looks like CLOUDSTACK-528   is related to 
> the same issue.

Fantastic!  Thank you Kishan.  Wei has been chugging away at the other
bugs, so we're getting there.

I'll send out an updated list of issues this afternoon.  There are still
others up for grabs folks...  come fix 'em!


> 
> ~kishan
> 
> > -----Original Message-----
> > From: Chip Childers [mailto:chip.child...@sungard.com]
> > Sent: Monday, 6 May 2013 10:07 PM
> > To: dev@cloudstack.apache.org
> > Subject: [ACS41] Outstanding issues to resolve
> > 
> > Once again, here's the list of issues for 4.1.0 that need to be addressed
> > before I try to re-spin an RC:
> > 
> > CLOUDSTACK-528  Failed to create secondary storage  Unassigned  Tamas
> > Monos
> > CLOUDSTACK-2309 Upgrade from 2.2.14 to 4.1.0 : network static routes
> > deleted on SSVM    Unassigned  Nicolas Lamirault
> > CLOUDSTACK-2319 2.2.14 to 4.1.0 upgrade: unable to add egress rules Wei
> > Zhou    Shashi Dahal
> > CLOUDSTACK-1907 Can't create system VM on XCP1.6 hypervisor Unassigned
> > Nikita Gubenko
> > CLOUDSTACK-2218 [web.context.ContextLoader] (main:null) Context
> > initialization failed   Unassigned  terryye
> > CLOUDSTACK-2318 upgrade from 2.2.14 -> 4.1.0 : unable to start an existing
> > running vm after stopping it manually    Unassigned  Shashi Dahal
> > CLOUDSTACK-2322 2.2.14 to 4.1.0 upgrade: unable to add a new VM Wei
> > Zhou    Shashi Dahal
> > 
> > As of right now, only 2322 and 2319 are assigned (Thanks for jumping on
> > them Wei!).
> > 
> > Assistance getting through this list, as well as any other upgrade problems
> > that are found, would be very much appreciated.
> > 
> > -chip
> 

Reply via email to