[
https://issues.apache.org/jira/browse/CLOUDSTACK-3190?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13839163#comment-13839163
]
Alex Ough commented on CLOUDSTACK-3190:
---------------------------------------
It looks like the information has been missed in master because it worked ok
during I was working on CLOUDSTACK-4992 with 4.2 codes, but now I don't have
them after switching the codes to master.
And after a little bit of investigation,
1. All the commands related with domain/account/user resources use the class
instance for the keys when storing the the 'entity uuid' as below.
CallContext.current().putContextParameter(Account.class, account.getUuid());
2. But the ActionEventUtil class uses different key to get the 'entity uuid' as
below.
entityUuid = (String)context.getContextParameter(EntityUuid); // where
EntityUuid is defined as "entity_uuid"
So even if the uuids are stored in the context, they are failed to be retrieved
from the context.
> action events message published on 'event bus' should have the UUID of the
> entity for which event generated and event type
> --------------------------------------------------------------------------------------------------------------------------
>
> Key: CLOUDSTACK-3190
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3190
> Project: CloudStack
> Issue Type: Task
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Affects Versions: 4.1.0
> Environment: action events message published on 'event bus' should
> have the UUID of the entity for which event generated and entity type
> details. as well
> Events bus framework with current AMQP default implementation, has routing
> key with format 'Eventsource.EventCategory.EventType.EntityType.EntityUUID'.
> For action events, EntityUUDI is not populated. Fix would required to ensure
> entity UUID is used in forming the routing key.
> Reporter: Murali Reddy
> Labels: newbie
>
--
This message was sent by Atlassian JIRA
(v6.1#6144)
