Github user anshul1886 commented on the issue:
https://github.com/apache/cloudstack/pull/1278
@rafaelweingartner, Basically CallContext.current().getCallingAccount(); is
setting the proper context which is later used. If you have observed in code
all the api calls have a similar call before proceeding further. One random
example:
```java
@ActionEvent(eventType = EventTypes.EVENT_VOLUME_UPLOAD, eventDescription
= "uploading volume", async = true)
public VolumeVO uploadVolume(UploadVolumeCmd cmd) throws
ResourceAllocationException {
Account caller = CallContext.current().getCallingAccount();
```
For more details refer
https://cwiki.apache.org/confluence/display/CLOUDSTACK/Using+CallContext and
commits 7928963 and 11e1e58 which I have mentioned earlier.
Hopefully this clears your doubts.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---
