Sanjay,
Yep, I understand that the bug was for resource count for secondary
storage, but the causes and errors are similar to what I see for primary
storage.
Here are the information you requested.
{u'account': [{u'accounttype': 0,
u'cpuavailable': u'Unlimited',
u'cpulimit': u'Unlimited',
u'cputotal': 0,
u'domain': u'Prod',
u'domainid': u'c18ac2cf-f74c-45a3-a412-368ed0310686',
u'id': u'6c48bca4-7b9a-4939-a189-cfc7fe7229b2',
u'ipavailable': u'Unlimited',
u'iplimit': u'Unlimited',
u'iptotal': 1,
u'isdefault': False,
u'memoryavailable': u'Unlimited',
u'memorylimit': u'Unlimited',
u'memorytotal': 0,
u'name': u'Operations',
u'networkavailable': u'Unlimited',
u'networklimit': u'Unlimited',
u'networktotal': 1,
* u'primarystorageavailable': u'Unlimited',**
** u'primarystoragelimit': u'Unlimited',**
** u'primarystoragetotal': 236,*
u'projectavailable': u'Unlimited',
u'projectlimit': u'Unlimited',
u'projecttotal': 0,
u'receivedbytes': 3133532,
u'secondarystorageavailable': u'Unlimited',
u'secondarystoragelimit': u'Unlimited',
u'secondarystoragetotal': 0,
u'sentbytes': 87766,
u'snapshotavailable': u'Unlimited',
u'snapshotlimit': u'Unlimited',
u'snapshottotal': 0,
u'state': u'enabled',
u'templateavailable': u'Unlimited',
u'templatelimit': u'Unlimited',
u'templatetotal': 0,
u'user': [{u'account': u'Operations',
There is currently no VMs running for this account, and the command
outputs 236GB. So when I try to spin a new VM I get:
Maximum number of resources of type 'primary_storage' for account
name=Operations in domain id=2 has been exceeded.
Let me know if you need more info. The bug seems identical to the one
identified for the secondary storage.
Thanks!
Francois
On 1/31/2014, 1:59 AM, Sanjay Tripathi wrote:
Francois,
Bug CLOUDSTACK-5406 was related to snapshot size and secondary storage
count.
For your issue, can you paste the response of listAccounts API for the
account you are trying to deploy VM with; this will help us to check
the resource_limit set for your account and what is the resource_count
that account is having.
Also paste the error message you are getting during the VM deployment.
--Sanjay
*From:*Francois Gaudreault [mailto:fgaudrea...@cloudops.com]
*Sent:* Friday, January 31, 2014 10:58 AM
*To:* Sanjay Tripathi
*Cc:* dev@cloudstack.apache.org; Sangeetha Hariharan; Animesh Chaturvedi
*Subject:* RE: CLOUDSTACK-5406
No, its the same thing as the ticket describe. I tried to lunch a VM,
and the resource limit was reached for my account even if there was no
volume running at all.
FG
On Jan 31, 2014 12:15 AM, "Sanjay Tripathi"
<sanjay.tripa...@citrix.com <mailto:sanjay.tripa...@citrix.com>> wrote:
Hi Francois,
Can you please explain what is the impact you are seeing in
primary storage count. Is it the negative value of primary storage
count or something else.
--Sanjay
-----Original Message-----
From: Animesh Chaturvedi
Sent: Friday, January 31, 2014 5:23 AM
To: dev@cloudstack.apache.org <mailto:dev@cloudstack.apache.org>;
fgaudrea...@cloudops.com <mailto:fgaudrea...@cloudops.com>
Cc: Sangeetha Hariharan; Sanjay Tripathi
Subject: RE: CLOUDSTACK-5406
Copying the folks that worked on it
-----Original Message-----
From: Francois Gaudreault [mailto:fgaudrea...@cloudops.com
<mailto:fgaudrea...@cloudops.com>]
Sent: Thursday, January 30, 2014 3:49 PM
To: dev@cloudstack.apache.org <mailto:dev@cloudstack.apache.org>
Subject: CLOUDSTACK-5406
Hi,
I saw this bug as been fixed for the secondary storage limits in 4.3:
CLOUDSTACK-5406
But it seems to impact the primary storage limit count as well, at
least in 4.2.1. Is the primary storage count fixed in 4.3 (I can't
test right
now) as well?
Thanks!
--
Francois Gaudreault
Architecte de Solution Cloud | Cloud Solutions Architect
fgaudrea...@cloudops.com <mailto:fgaudrea...@cloudops.com>
514-629-6775 <tel:514-629-6775>
- - -
CloudOps
420 rue Guy
Montréal QC H3J 1S6
www.cloudops.com <http://www.cloudops.com>
@CloudOps_
--
Francois Gaudreault
Architecte de Solution Cloud | Cloud Solutions Architect
fgaudrea...@cloudops.com
514-629-6775
- - -
CloudOps
420 rue Guy
Montréal QC H3J 1S6
www.cloudops.com
@CloudOps_
