You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cloudstack.apache.org by "venkata swamybabu budumuru (JIRA)" <ji...@apache.org> on 2013/07/19 13:12:48 UTC
[jira] [Updated] (CLOUDSTACK-3666) deployVMCmd is failing in case
of incorrect AMQP server credentials in nonosscomponentContext.xml
[ https://issues.apache.org/jira/browse/CLOUDSTACK-3666?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
venkata swamybabu budumuru updated CLOUDSTACK-3666:
---------------------------------------------------
Priority: Major (was: Minor)
Summary: deployVMCmd is failing in case of incorrect AMQP server credentials in nonosscomponentContext.xml (was: deployVMCmd is failing in case of incorrect AMQP server credentials in nonosscomponentContext.xml
)
> deployVMCmd is failing in case of incorrect AMQP server credentials in nonosscomponentContext.xml
> -------------------------------------------------------------------------------------------------
>
> Key: CLOUDSTACK-3666
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3666
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the default.)
> Reporter: venkata swamybabu budumuru
>
> Steps to reproduce:
> (1) Have latest CloudStack setup with at least one advanced zone.
> (2) Change the following settings in nonosscomponentContext.xml
> <bean id="eventNotificationBus" class="org.apache.cloudstack.mom.rabbitmq.RabbitMQEventBus">
> <property name="name" value="eventNotificationBus"/>
> <property name="server" value="10.147.60.13"/>
> <property name="port" value="15672"/>
> <property name="username" value="guest"/>
> <property name="password" value="guest"/>
> <property name="exchange" value="cloudstack-events"/>
> </bean>
> (3) restart the management server after the above changes.
> (4) deploy a VirtualMachine
> Observations:
> (i) VM deployment fails with the following error in mgmt server logs.
> 2013-07-19 16:34:28,182 DEBUG [agent.transport.Request] (RedundantRouterStatusMonitor-7:null) Seq 1-157614346: Received: { Ans: , MgmtId: 7280707764394, via: 1, Ver: v1, Flags: 10, { CheckRouterAnswer } }
> 2013-07-19 16:34:28,182 DEBUG [agent.manager.AgentManagerImpl] (RedundantRouterStatusMonitor-7:null) Details from executing class com.cloud.agent.api.CheckRouterCommand: Status: BACKUP&Bumped: NO
> 2013-07-19 16:34:30,948 ERROR [mom.rabbitmq.RabbitMQEventBus] (catalina-exec-17:null) Failed to create a connection to AMQP server due to Possibly caused by authentication failure
> 2013-07-19 16:34:30,948 WARN [cloud.async.AsyncJobManagerImpl] (catalina-exec-17:null) Failed to publish async job event on the the event bus.
> org.apache.cloudstack.framework.events.EventBusException: Failed to publish event to message broker due to Possibly caused by authentication failure
> 2013-07-19 16:34:30,951 WARN [cloud.async.AsyncJobManagerImpl] (catalina-exec-17:null) Unable to schedule async job for command org.apache.cloudstack.api.command.user.vm.DeployVMCmd, unexpected exception.
> com.cloud.utils.exception.CloudRuntimeException: Failed to publish async job event on the the event bus.
> at com.cloud.async.AsyncJobManagerImpl.publishOnEventBus(AsyncJobManagerImpl.java:193)
> at com.cloud.async.AsyncJobManagerImpl.submitAsyncJob(AsyncJobManagerImpl.java:217)
> 2013-07-19 16:34:30,952 ERROR [cloud.api.ApiServer] (catalina-exec-17:null) unhandled exception executing api command: deployVirtualMachine
> com.cloud.utils.exception.CloudRuntimeException: Unable to schedule async job for command org.apache.cloudstack.api.command.user.vm.DeployVMCmd, unexpected exception.
> at com.cloud.async.AsyncJobManagerImpl.submitAsyncJob(AsyncJobManagerImpl.java:223)
> at com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125)
> at com.cloud.async.AsyncJobManagerImpl.submitAsyncJob(AsyncJobManagerImpl.java:199)
> Attaching all the required logs along with db dump to the bug.
--
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