cloudstack-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF subversion and git services (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CLOUDSTACK-3239) deleteTrafficMonitor API fails with NPE
Date Fri, 28 Jun 2013 05:48:20 GMT

    [ https://issues.apache.org/jira/browse/CLOUDSTACK-3239?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13695272#comment-13695272
] 

ASF subversion and git services commented on CLOUDSTACK-3239:
-------------------------------------------------------------

Commit 7713c5cdbc07580583f57434306614eedcc4c5ef in branch refs/heads/master from [~kishan]
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=7713c5c ]

CLOUDSTACK-3239: Delete Traffic Monitor directly without going through maintenance state

                
> deleteTrafficMonitor API fails with NPE
> ---------------------------------------
>
>                 Key: CLOUDSTACK-3239
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3239
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the default.) 
>          Components: Usage
>    Affects Versions: 4.2.0
>            Reporter: Kishan Kavala
>            Assignee: Kishan Kavala
>             Fix For: 4.2.0
>
>
> Steps:
> 1.Add the trafficsentinal host into cloudstack
> http://10.147.39.54:8096/client/api?command=addTrafficMonitor&url=http%3A%2F%2F10.147.39.36&zoneid=1
> 2.Once its registered successful,delete the added host using deleteTrafficMonitor host

> http://10.147.39.54:8096/client/api?command=deleteTrafficMonitor&id=9
> 2012-09-05 12:18:24,583 DEBUG [dc.dao.DataCenterIpAddressDaoImpl] (ApiServer-6:null)
Releasing ip address: 10.147.39.36 data center 1
> 2012-09-05 12:18:24,587 DEBUG [cloud.resource.ResourceManagerImpl] (ApiServer-6:null)
Cannot transmit host 9to Enabled state
> com.cloud.utils.fsm.NoTransitionException: No next resource state found for current state
=PrepareForMaintenance event =DeleteHost
>         at com.cloud.resource.ResourceManagerImpl.resourceStateTransitTo(ResourceManagerImpl.java:1175)
>         at com.cloud.resource.ResourceManagerImpl.doDeleteHost(ResourceManagerImpl.java:887)
>         at com.cloud.utils.db.DatabaseCallback.intercept(DatabaseCallback.java:30)
>         at com.cloud.resource.ResourceManagerImpl.deleteHost(ResourceManagerImpl.java:929)
>         at com.cloud.network.NetworkUsageManagerImpl.deleteTrafficMonitor(NetworkUsageManagerImpl.java:189)
>         at com.cloud.api.commands.DeleteTrafficMonitorCmd.execute(DeleteTrafficMonitorCmd.java:70)
>         at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:235)
>         at com.cloud.api.ApiServer.queueCommand(ApiServer.java:540)
>         at com.cloud.api.ApiServer.handleRequest(ApiServer.java:419)
>         at com.cloud.api.ApiServer.handle(ApiServer.java:349)
>         at org.apache.http.protocol.HttpService.doService(HttpService.java:293)
>         at org.apache.http.protocol.HttpService.handleRequest(HttpService.java:212)
>         at com.cloud.api.ApiServer$WorkerTask.run(ApiServer.java:996)
>         at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
>         at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
>         at java.lang.Thread.run(Thread.java:679)

--
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