Closed natea closed 14 years ago
It will be fixed in 0.8, it was a stupid mistake during refactoring on my part. It's also nothing serious, the startup is all done at the point this error comes up, just run the status command manually to get the same info you would have got at the end of the start command.
Since updating to the latest mr.awsome 0.6, now when I run the ./bin/aws start command, the following error occurs. Do I need to pass in another argument besides the server config that I want to use?
{{{ $ ./bin/aws start test INFO: Instance 'test' unavailable INFO: Creating instance 'test' INFO: Instance created, waiting until it's available ... Traceback (most recent call last): File "./bin/aws", line 16, in
mr.awsome.aws(configpath="/Users/nateaune/code/mrawsome.buildout/etc/deployment")
File "/Users/nateaune/.buildout/eggs/mr.awsome-0.6-py2.6.egg/mr/awsome/init.py", line 652, in aws
return aws(argv)
File "/Users/nateaune/.buildout/eggs/mr.awsome-0.6-py2.6.egg/mr/awsome/init.py", line 646, in call
args.func(sub_argv, args.func.doc)
File "/Users/nateaune/.buildout/eggs/mr.awsome-0.6-py2.6.egg/mr/awsome/init.py", line 444, in cmd_start
self.cmd_status()
TypeError: cmd_status() takes exactly 3 arguments (1 given)
}}}