[
https://issues.apache.org/jira/browse/CLOUDSTACK-1673?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13724867#comment-13724867
]
Murali Reddy commented on CLOUDSTACK-1673:
------------------------------------------
Should have mentioned this earlier when i closed the bug. My bad. So for an
API, three events are raised corresponding state of async job for the API. When
job is scheduled, started and completed. At the stage of schedule and started,
entity is not created at all. Only when all validations are passed and entity
is created, there is UUID for the entity. Thats region only event for
'Completed' job has UUID.
In the context of regions account sync, its good enough the watch for the
completed events and propagate the account/user/domains.
> AWS Regions - Events - User disable / Domain Delete event does not include
> the UUID of the user/domain that was disabled.
> -------------------------------------------------------------------------------------------------------------------------
>
> Key: CLOUDSTACK-1673
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1673
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: Management Server
> Affects Versions: 4.1.0, 4.2.0
> Environment: Latest build from 4.1
> Reporter: Sangeetha Hariharan
> Assignee: Murali Reddy
> Priority: Critical
> Fix For: 4.2.0
>
>
> AWS Regions - Events - User disable / Domain Delete event does not include
> the UUID of the user/domain that was disabled
> Scenario 1:
> Pre Req:
> 1. Configure Management server to point to RabbitMQ server for event
> notifications.
> Steps:
> 1. Disable one of the existing users.
> Following is the payload of the event that gets published:
> {"status":"Scheduled","event":"USER.DISABLE","account":"1be7e5f7-7a3f-467c-b30d-4d6f834254d9","user":"3ff1190e-5aa3-4551-9cb3-a97db0bd0d51"}
> UUID of the user that was disabled is NOT included in the payload. The user
> that is present in the payload is the admin user i was logged in as when I
> performed the disable action. Account that is passed is the account that the
> user that is disabled belongs to.
> mysql> select * from user where uuid="3ff1190e-5aa3-4551-9cb3-a97db0bd0d51";
> +----+--------------------------------------+----------+----------------------------------+------------+-----------+----------+------------------+---------+---------+------------+---------------------+---------+---------------------+--------------------+---------------+--------------------------+-----------+
> | id | uuid | username | password
> | account_id | firstname | lastname | email | state
> | api_key | secret_key | created | removed | timezone
> | registration_token | is_registered | incorrect_login_attempts | region_id |
> +----+--------------------------------------+----------+----------------------------------+------------+-----------+----------+------------------+---------+---------+------------+---------------------+---------+---------------------+--------------------+---------------+--------------------------+-----------+
> | 18 | 3ff1190e-5aa3-4551-9cb3-a97db0bd0d51 | san-adm1 |
> a072a11d146e3ff670cb4e43af5cdcc7 | 10 | san-adm1 | san-adm1 |
> [email protected] | enabled | NULL | NULL | 2013-03-13 22:58:24 |
> NULL | America/Los_Angeles | NULL | 0 |
> 0 | 1 |
> +----+--------------------------------------+----------+----------------------------------+------------+-----------+----------+------------------+---------+---------+------------+---------------------+---------+---------------------+--------------------+---------------+--------------------------+-----------+
> 1 row in set (0.00 sec)
> mysql> select * from user where uuid="c6ca317e-386e-43eb-8892-a702807e1935";
> +----+--------------------------------------+------------+----------------------------------+------------+----------------+----------------+--------------------+----------+---------+------------+---------------------+---------+---------------------+--------------------+---------------+--------------------------+-----------+
> | id | uuid | username | password
> | account_id | firstname | lastname | email
> | state | api_key | secret_key | created | removed |
> timezone | registration_token | is_registered |
> incorrect_login_attempts | region_id |
> +----+--------------------------------------+------------+----------------------------------+------------+----------------+----------------+--------------------+----------+---------+------------+---------------------+---------+---------------------+--------------------+---------------+--------------------------+-----------+
> | 4 | c6ca317e-386e-43eb-8892-a702807e1935 | san-test11 |
> 53d9012c4b85f29b8ff5c5c3606e9d62 | 4 | san-test113456 |
> san-test113456 | [email protected] | disabled | NULL | NULL |
> 2013-03-06 19:35:54 | NULL | America/Los_Angeles | NULL |
> 0 | 0 | 1 |
> +----+--------------------------------------+------------+----------------------------------+------------+----------------+----------------+--------------------+----------+---------+------------+---------------------+---------+---------------------+--------------------+---------------+--------------------------+-----------+
> 1 row in set (0.00 sec)
> mysql>
> Scenario 2:
> AWS Regions - Events - Domain Delete event does not include the UUID of the
> domain that was deleted.
> Pre Req:
> 1. Configure Management server to point to RabbitMQ server for event
> notifications.
> Steps:
> 1. Delete an existing domain.
> Following is the payload of the event that gets prublished:
> {"status":"Scheduled","event":"DOMAIN.DELETE","account":"875cc6a8-8688-11e2-89d9-06d4460004b1","user":"875d71d4-8688-11e2-89d9-06d4460004b1"}
> This event does not include the uuid of the domain that was deleted.
> event DB for this activity:
> | 65 | d873a6a4-e107-4033-96ed-af1d753c044f | DOMAIN.DELETE | Scheduled |
> deleting domain: 5 | 2 | 2 | 1 | 2013-03-13 18:54:05 | INFO | 0 | NULL |
> +----+--------------------------------------+---------------------------+-----------+---------------------------------------------------+---------+------------+-----------+---------------------+-------+----------+------------+
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
