No problem :) Sorry I didn't run that test case.
On Mon, Mar 10, 2014 at 12:08 PM, Nitin Mehta wrote:
> Thanks Mike for the prompt response :).
>
> On 10/03/14 10:44 AM, "Mike Tutkowski"
> wrote:
>
> >1d74daf has the fix.
> >
> >Thanks!
> >
> >
> >On Mon, Mar 10, 2014 at 11:42 AM, Mike Tutkowsk
Thanks Mike for the prompt response :).
On 10/03/14 10:44 AM, "Mike Tutkowski"
wrote:
>1d74daf has the fix.
>
>Thanks!
>
>
>On Mon, Mar 10, 2014 at 11:42 AM, Mike Tutkowski <
>mike.tutkow...@solidfire.com> wrote:
>
>> OK, I'm sorry about that - I missed a case in testing.
>>
>> Line 191 in Cloud
1d74daf has the fix.
Thanks!
On Mon, Mar 10, 2014 at 11:42 AM, Mike Tutkowski <
mike.tutkow...@solidfire.com> wrote:
> OK, I'm sorry about that - I missed a case in testing.
>
> Line 191 in CloudOrchestrator should be this:
>
> if (offering.isCustomizedIops() != null && offering.isCustomizedIop
OK, I'm sorry about that - I missed a case in testing.
Line 191 in CloudOrchestrator should be this:
if (offering.isCustomizedIops() != null && offering.isCustomizedIops()) {
isCustomizedIops() returns a Boolean - not a boolean.
I'll check in this fix right now.
On Mon, Mar 10, 2014 at 11:32
Let me see if I can repro it.
One sec
On Mon, Mar 10, 2014 at 11:11 AM, Nitin Mehta wrote:
> I am facing the same issue as well.
>
> On 10/03/14 10:09 AM, "Koushik Das" wrote:
>
> >This is a new install using master. So this is not about db changes but
> >mostly a bug.
> >
> >On 10-Mar-2014, a
I am facing the same issue as well.
On 10/03/14 10:09 AM, "Koushik Das" wrote:
>This is a new install using master. So this is not about db changes but
>mostly a bug.
>
>On 10-Mar-2014, at 9:58 PM, Marcus wrote:
>
>> Mike has sent out several emails about the DB changes he made.
>>
>> On Mon,
This is a new install using master. So this is not about db changes but mostly
a bug.
On 10-Mar-2014, at 9:58 PM, Marcus wrote:
> Mike has sent out several emails about the DB changes he made.
>
> On Mon, Mar 10, 2014 at 5:28 AM, Koushik Das wrote:
>> I am seeing the following exception
>>
>
Mike has sent out several emails about the DB changes he made.
On Mon, Mar 10, 2014 at 5:28 AM, Koushik Das wrote:
> I am seeing the following exception
>
> ERROR [c.c.a.ApiServer] (38419149@qtp-1917357200-11:ctx-116b8207
> ctx-9a54f764) unhandled exception executing api command:
> [Ljava.lang.