[
https://issues.apache.org/jira/browse/CLOUDSTACK-1357?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13583085#comment-13583085
]
Vijay Venkatachalam commented on CLOUDSTACK-1357:
-------------------------------------------------
jobstatus is returned as part of the virtual machine object also in addition to
the actual job status.
Please see comments below marked as *******
<queryasyncjobresultresponse cloud-stack-version="4.1.0-SNAPSHOT">
<accountid>7ce999d6-7a75-11e2-b143-b22b29d9539b</accountid>
<userid>7ce9c456-7a75-11e2-b143-b22b29d9539b</userid>
<cmd>
org.apache.cloudstack.api.command.user.vm.DeployVMCmd
</cmd>
<jobstatus>1</jobstatus>
<!-- ******* Correct One *******>
<jobprocstatus>0</jobprocstatus>
<jobresultcode>0</jobresultcode>
<jobresulttype>object</jobresulttype>
<hypervisor>XenServer</hypervisor>
<instancename>i-2-54-VM</instancename>
<!-- ******* The below one has to be removed *******>
<jobstatus>0</jobstatus>
</virtualmachine>
</jobresult>
<created>2013-02-21T13:04:24+0530</created>
<jobid>ad461552-a3ad-4bac-80b7-1965a4d9f688</jobid>
</queryasyncjobresultresponse>
This is because of the api refactoring/optimization code, commit id b0ce8fd4.
The code that has to be removed in the file
server/src/com/cloud/api/query/dao/UserVmJoinDaoImpl.java
in Line number 136
Please note there are other entities (StoragePools/Volumes...) where this
problem exists because of the apirefactoring (may be copy paste errror!!)
> Autoscale: Provisioned VMs from Netscaler not being added to lb vserver,
> provserver fails with provserver_err_asynctaskpoll
> ---------------------------------------------------------------------------------------------------------------------------
>
> Key: CLOUDSTACK-1357
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1357
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: Network Devices
> Affects Versions: 4.1.0
> Environment: Ubuntu 11.10, XS 6.1, Netscaler v 10.0
> Reporter: Sowmya Krishnan
> Assignee: Vijay Venkatachalam
> Priority: Blocker
> Fix For: 4.1.0
>
> Attachments: nslog
>
>
> VMs are getting provisioned but are not getting added to the lb vserver. DNS
> records not created either. Following is the provision log from ns.log:
> Feb 21 07:02:29 <local0.notice> ns provserverd[393]: Job provision request
> for Service Group (Cloudabc622303efb4ebe9ad4fa272103e2fd)
> Feb 21 07:02:34 <local0.info> 10.102.192.50 02/21/2013:07:02:34 GMT 0-PPE-0
> : UI CMD_EXECUTED 3108 0 : User nsroot - Remote_ip 10.144.7.15 - Command
> "show lb vserver Cloud-VirtualServer-1
> 0.102.196.245-22" - Status "Success"
> Feb 21 07:02:59 <local0.warn> ns provserverd[393]: Job with job type (0) for
> Service Group (Cloudabc622303efb4ebe9ad4fa272103e2fd) -> Error :
> provserver_err_asynctaskpoll
> Feb 21 07:03:29 <local0.notice> ns provserverd[393]: Job provision request
> for Service Group (Cloudabc622303efb4ebe9ad4fa272103e2fd)
> Steps
> =====
> 1. Create an Autoscale config with suitable template and min members as 2 and
> max as 5. Set appropriate scale up and scale down policies
> 2. Verify lb rule is created in Netscaler
> Result
> =====
> Status of lb vserver is DOWN and dns record is not added for the deployed VM.
> VMs continue to get deployed but it is not getting added to the lb vserver
> Expected Result
> =============
> 2 VMs should be provisioned and added to lb vserver and dns records for the
> VMs should get added as well.
> lb vserver status should be UP and so should the services.
--
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
