; Alex Huang
Subject: Re: deleteAffinityGroup API
All of our tests go over 8080, I explained this to Prachi last night over IRC.
The logs I picked out oddly had only system-background threads. I'll add more
relevant logs.
or you can run the test_affinity_groups.py tests against a simulator run
, July 18, 2013 4:13 PM
> To: dev@cloudstack.apache.org; Prachi Damle; Alex Huang
> Subject: Re: deleteAffinityGroup API
>
> If the API came through port 8096, then the caller comes as a System context
> (System default user id=1, account id=1). It was always like this since the
> time the UserC
: deleteAffinityGroup API
Prachi,
Unrelated to the bug, I also want to ask why do we check for system account in
this case. In CloudStack System context should have the same privileges as an
admin.Why in this specific case we check for system account and deny access?
--Alex
> -Original Mess
; From: Prachi Damle
> Sent: Thursday, July 18, 2013 11:55 AM
> To: dev@cloudstack.apache.org
> Cc: Alex Huang
> Subject: RE: deleteAffinityGroup API
>
> Hi Alex,
>
> The error thrown while deleting affinitygroup by Id is: " Account and
> domainId are needed for resour
Prasanna does the regression test scripts call using 8096 port?
If yes then that's the reason why the API is failing.
From: Alena Prokharchyk
Sent: Thursday, July 18, 2013 4:13 PM
To: dev@cloudstack.apache.org; Prachi Damle; Alex Huang
Subject: Re: deleteAffinityGroup API
If the API
<mailto:dev@cloudstack.apache.org>"
mailto:dev@cloudstack.apache.org>>
Date: Thursday, July 18, 2013 4:00 PM
To: Prachi Damle mailto:prachi.da...@citrix.com>>,
"dev@cloudstack.apache.org<mailto:dev@cloudstack.apache.org>"
mailto:dev@cloudstack.apache.org>
h admin API, it came
in as System context. That would be a bug if I understand you correctly.
--Alex
> -Original Message-
> From: Prachi Damle
> Sent: Thursday, July 18, 2013 11:55 AM
> To: dev@cloudstack.apache.org
> Cc: Alex Huang
> Subject: RE: deleteAffinityGroup
the subsequent failure. Why would it return system user, if the caller
is admin user?
Thanks,
Prachi
-Original Message-
From: Prasanna Santhanam [mailto:t...@apache.org]
Sent: Thursday, July 18, 2013 6:09 AM
To: dev@cloudstack.apache.org
Subject: Re: deleteAffinityGroup API
On Thu, Jul 18
On Thu, Jul 18, 2013 at 02:17:46PM +0530, Prasanna Santhanam wrote:
> On Thu, Jul 18, 2013 at 07:14:42AM +, Prachi Damle wrote:
> > Account and domainId are not required parameters of this API. It
> > works fine with just an id too.
> >
> > Account and domain will be used if delete is called p
On Thu, Jul 18, 2013 at 07:14:42AM +, Prachi Damle wrote:
> Account and domainId are not required parameters of this API. It
> works fine with just an id too.
>
> Account and domain will be used if delete is called providing a name
> of the group instead of id, say by an admin for a regular us
hanam [mailto:t...@apache.org]
Sent: Wednesday, July 17, 2013 10:12 PM
To: CloudStack Dev
Subject: deleteAffinityGroup API
This API unlike all the other delete APIs in cloudstack needs an account and
domainid to delete the cloud resource (affinity group).
Any reason why this should flout the semanti
This API unlike all the other delete APIs in cloudstack needs an
account and domainid to delete the cloud resource (affinity group).
Any reason why this should flout the semantics of other delete APIs
which work with just an id?
Signature below:
AffinityGroupServiceImpl.java
@DB
@Override
12 matches
Mail list logo
