On Jul 1, 2013, at 3:01 AM, Thomas O'Dowd <tpod...@cloudian.com> wrote:
> Thanks Prasanna, > > I reset the devcloud image back to its initial state (fresh copy of the > downloaded image) to get rid of anything that might be in a bad state. > Then rebuilt, deployed etc but I get the same problem. Do I need to > clean up something in addition on my development machine? > > Thanks, > > Tom. Tom, looks like you solved this by importing devcloud form scratch. The testing procedure has some instructions about cleaning up the environment, that might help next time: https://cwiki.apache.org/confluence/display/CLOUDSTACK/CloudStack+4.0+test+procedure > > On Mon, 2013-07-01 at 11:12 +0530, Prasanna Santhanam wrote: >> On Mon, Jul 01, 2013 at 02:26:26PM +0900, Thomas O'Dowd wrote: >>> Hi all, >>> >>> checked out 4.2 branch today. New build, deploydb and start management >>> server. then deploysvr... on the management server terminal logs, I can >>> see a new exception that wasn't on master last week. >>> >> >>> The system vms do eventually get launched but when I stop them and >>> restart the management server it never starts them again. >>> >>> Any ideas? I've been testing with devcloud like this for a while now so >>> I don't think it's something I'm doing. >>> >> I reset the devcloud image to the base snapshot on virtualbox and >> rebuilt on 4.2 and didn't find any exceptions. Then I stopped >> management server, and destroyed my systemVMs and they came back up >> fine. >> >> Edison mentioned the issue was with systemvm.iso last week >> http://markmail.org/message/c4ihlzu7lxohhc5k >> >> Can you retry by reseting devcloud? >> > > -- > Cloudian KK - http://www.cloudian.com/get-started.html > Fancy 100TB of full featured S3 Storage? > Checkout the Cloudian® Community Edition! >
