cloudstack-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sangeetha Hariharan (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (CLOUDSTACK-1775) AWS Regions - Events Framework - Events relating to User/Domain/Account are not being published to the RabbitMQ server expect for USER-DISABLE,DOMAIN-DELETE and ACCOUNT.DISABLE event.
Date Fri, 22 Mar 2013 17:29:15 GMT

     [ https://issues.apache.org/jira/browse/CLOUDSTACK-1775?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Sangeetha Hariharan updated CLOUDSTACK-1775:
--------------------------------------------

    Fix Version/s:     (was: 4.1.1)
                   4.1.0
    
> AWS Regions - Events Framework - Events relating to User/Domain/Account are not being
published to the RabbitMQ server expect for USER-DISABLE,DOMAIN-DELETE and ACCOUNT.DISABLE
event.
> ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: CLOUDSTACK-1775
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1775
>             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
>         Environment: Build from 4.1
>            Reporter: Sangeetha Hariharan
>            Assignee: Murali Reddy
>            Priority: Blocker
>             Fix For: 4.1.0
>
>
> AWS Regions - Events Framework - Events relating to User/Domain/Account are not being
published to the RabbitMQ server expect for USER-DISABLE,DOMAIN-DELETE and ACCOUNT.DISABLE
event.
> Steps to reproduce the problem:
> Have a RabbitMQ server set up.
> Enable rabbitmq_management plugin
>  
> C:\Program Files\RabbitMQ Server\rabbitmq_server-3.0.3\sbin>rabbitmq-plugins enable
rabbitmq_management
> Restart RabbitMQ service.
> In management server :
> Added the following in /usr/share/cloudstack-management/webapps/client/WEB-INF/classes/componentContext.xml
>         <bean id="eventNotificationBus" class="org.apache.cloudstack.mom.rabbitmq.RabbitMQEventBus">
>     <property name="name" value="eventNotificationBus"/>
>     <property name="server" value="10.210.224.156"/>
>     <property name="port" value="5672"/>
>     <property name="username" value="guest"/>
>     <property name="password" value="guest"/>
>    <property name="exchange" value="cloudstack-events"/>
>   </bean>
> Restart management server.
> We  see cloudstack-event exchange beinf created automatically.
> create a 'queue' and bind it to this exchange, with binding key *.*.*.*.* . "
> For any action on User/Domain/Account objects  we do not see the any event being published
to the RabbitMQ server expect for USER-DISABLE,DOMAIN-DELETE and ACCOUNT.DISABLE event.
> In the events table , I do see events being created for the following actions , but no
events being published to RabbitMQ server.
> 1. Create Account
> 2. Create Domain
> 3. Update Diomain
> 4. Delete Domain
> 5.  Enabling User
> 6.  Updating User 
>  2 |          2 |         1 | 2013-03-21 23:00:38 | INFO  |        0 | NULL       |
> |  96 | 0529b3e1-75f0-4e89-866b-00838915057c | ACCOUNT.CREATE            | Completed
| Successfully completed creating Account. Account Name: new-acct, Domain Id:1  |        
 2 |          1 |         1 | 2013-03-21 23:03:45 | INFO  |        0 | NULL       |
> |  97 | 7794f59a-2693-49d1-a54f-881fb2ca3b7d | ACCOUNT.DISABLE           | Scheduled
| disabling account: new-acct in domain: 1                                      |        
 2 |         11 |         1 | 2013-03-21 23:05:11 | INFO  |        0 | NULL       |
> |  98 | 24a0e343-8613-4027-85d2-cace9510556f | ACCOUNT.DISABLE           | Started  
| Starting job for disabling account. Account Name: new-acct, Domain Id:1       |        
 2 |         11 |         1 | 2013-03-21 23:05:11 | INFO  |       97 | NULL       |
> |  99 | 3242683f-2d11-4863-8e11-7b47fdcee6ec | ACCOUNT.DISABLE           | Completed
| Successfully completed disabling account. Account Name: new-acct, Domain Id:1 |        
 2 |         11 |         1 | 2013-03-21 23:05:11 | INFO  |       97 | NULL       |
> | 100 | a40f0e47-8d58-482a-ac66-50ca17032cb6 | DOMAIN.CREATE             | Completed
| Successfully completed creating Domain. Domain Name: dom1, Parent DomainId :1 |        
 2 |          1 |         1 | 2013-03-21 23:39:25 | INFO  |        0 | NULL       |
> | 101 | 57031b15-2fb3-4dd5-ad58-04bf50a97f26 | DOMAIN.UPDATE             | Completed
| Successfully completed updating Domain. Domain Id: 5                          |        
 2 |          1 |         1 | 2013-03-21 23:40:24 | INFO  |        0 | NULL       |
> | 102 | efd5848f-35c4-49c6-939c-ed2104c845c0 | DOMAIN.DELETE             | Scheduled
| deleting domain: 5                                                            |        
 2 |          2 |         1 | 2013-03-21 23:40:45 | INFO  |        0 | NULL       |
> | 103 | e64b3b91-e648-48da-a990-104570e167af | DOMAIN.DELETE             | Started  
| Starting job for deleting Domain. Domain Id: 5                                |        
 2 |          2 |         1 | 2013-03-21 23:40:45 | INFO  |      102 | NULL       |
> | 104 | 1e795d00-3446-43cc-ab8f-1bf36c019db0 | DOMAIN.DELETE             | Completed
| Successfully completed deleting Domain. Domain Id: 5                          |        
 2 |          2 |         1 | 2013-03-21 23:40:45 | INFO  |      102 | NULL       |
> | 105 | ef4b3a5a-21c5-4c63-a6e4-2c04bcc2cb26 | DOMAIN.UPDATE             | Completed
| Successfully completed updating Domain. Domain Id: 3                          |        
 2 |          1 |         1 | 2013-03-21 23:55:17 | INFO  |        0 | NULL       |
> | 106 | 2bff9a8d-4e45-40d2-8db2-fa23c49271f4 | USER.DISABLE              | Scheduled
| disabling user: 14                                                            |        
 2 |          3 |         2 | 2013-03-21 23:56:33 | INFO  |        0 | NULL       |
> | 107 | 90062448-36c8-48be-8ed4-aa6f8b39dee1 | USER.DISABLE              | Started  
| Starting job for disabling User. UserId: 14                                   |        
 2 |          3 |         2 | 2013-03-21 23:56:33 | INFO  |      106 | NULL       |
> | 108 | bf9abdad-681c-4013-a4c5-3f3fd326653c | USER.DISABLE              | Completed
| Successfully completed disabling User. UserId: 14                             |        
 2 |          3 |         2 | 2013-03-21 23:56:33 | INFO  |      106 | NULL       |
> | 109 | b5258435-f244-40a9-8838-5bcd6fcb8477 | USER.ENABLE               | Completed
| Successfully completed enabling User. UserId: 14                              |        
 2 |          3 |         2 | 2013-03-21 23:57:42 | INFO  |        0 | NULL       |
> | 110 | 450dacf4-3c4a-4dae-90bb-258c7daa40d8 | USER.UPDATE               | Completed
| Successfully completed updating User. UserId: 6                               |        
 2 |          3 |         2 | 2013-03-21 23:59:06 | 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

Mime
View raw message