Hi Mike,
This was caused by missing initialization of _maxVolumeSizeInGb from
configDao in configuring VolumeApiServiceImpl. I checked in a fix
694ec684a372c95abf8d1a798714b6f074862816 into master, which should have
fixed this issue.
Thanks
-min
On 10/24/13 4:35 PM, "Mike Tutkowski" <[email protected]> wrote:
>Figured I'd send this out again.
>
>Any thoughts as to why _maxVolumeSizeInGb is never assigned to in
>VolumeApiServiceImpl?
>
>The end result is you cannot create a volume unless you explicitly go into
>VolumeApiServiceImpl and do something like assign a high value to
>_maxVolumeSizeInGb.
>
>I opened a JIRA ticket for this issue:
>
>https://issues.apache.org/jira/browse/CLOUDSTACK-4812
>
>
>On Wed, Oct 2, 2013 at 1:48 PM, Mike Tutkowski
><[email protected]
>> wrote:
>
>> Hi,
>>
>> I'm trying to create a volume from a Disk Offering that specifies a 10
>>GB
>> disk.
>>
>> When attempting to create a volume from this Disk Offering, I'm told the
>> maximum size I can create for a volume is 0 GB.
>>
>> In VolumeApiServiceImpl, I see a private instance variable called
>> _maxVolumeSizeInGb, which appears to be the problem.
>>
>> It is read from, but never written to (its default value is 0 since it
>>is
>> a 'long' member variable).
>>
>> Am I missing something here?
>>
>> Thanks!
>>
>> --
>> *Mike Tutkowski*
>> *Senior CloudStack Developer, SolidFire Inc.*
>> e: [email protected]
>> o: 303.746.7302
>> Advancing the way the world uses the
>>cloud<http://solidfire.com/solution/overview/?video=play>
>> **
>>
>
>
>
>--
>*Mike Tutkowski*
>*Senior CloudStack Developer, SolidFire Inc.*
>e: [email protected]
>o: 303.746.7302
>Advancing the way the world uses the
>cloud<http://solidfire.com/solution/overview/?video=play>
>**
