On Fri, May 31, 2013 at 6:40 PM, Chip Childers wrote:
> On Fri, May 31, 2013 at 11:13:03AM +0530, Prasanna Santhanam wrote:
> > On Fri, May 31, 2013 at 01:49:02AM +, Soheil Eizadi wrote:
> > > I don't know if the following is a known issue, while testing some
> > > negative test case, I added
: Prasanna Santhanam [t...@apache.org]
Sent: Thursday, May 30, 2013 10:43 PM
To: dev@cloudstack.apache.org
Cc: bhais...@apache.org
Subject: Re: CloudMonkey handling of Job Status Error Code
On Fri, May 31, 2013 at 01:49:02AM +, Soheil Eizadi wrote:
> I don't know if the following is a known issu
On Fri, May 31, 2013 at 11:13:03AM +0530, Prasanna Santhanam wrote:
> On Fri, May 31, 2013 at 01:49:02AM +, Soheil Eizadi wrote:
> > I don't know if the following is a known issue, while testing some
> > negative test case, I added a device that was not part of network
> > provider associated w
On Fri, May 31, 2013 at 01:49:02AM +, Soheil Eizadi wrote:
> I don't know if the following is a known issue, while testing some
> negative test case, I added a device that was not part of network
> provider associated with the physical network from CloudMonkey, from
> the log I could see that t
I don't know if the following is a known issue, while testing some negative
test case, I added a device that was not part of network provider associated
with the physical network from CloudMonkey, from the log I could see that they
system returned an error as expected, but looks like CloudMonkey
