[
https://issues.apache.org/jira/browse/CLOUDSTACK-7324?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14105284#comment-14105284
]
Koushik Das commented on CLOUDSTACK-7324:
-----------------------------------------
As part of the job framework changes, a new type of internal job "VmWork" got
introduced. This is reusing the same async_job table which used to store only
the async api jobs previously. This additional data has resulted in the issue
described.
Possible solution - add a new filter parameter 'jobType'. This should be
defaulted to async api job to keep the old behaviour.
> listAsyncJobs returns jobs with no cmd
> --------------------------------------
>
> Key: CLOUDSTACK-7324
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7324
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: API
> Affects Versions: 4.4.0
> Reporter: Brian Angus
> Priority: Minor
>
> when running listAsyncJobs it will return jobids that do not have a cmd.
> Like this:{code}
> {
> "accountid": "72e70a88-18d8-11e4-98d6-5254004eff4f",
> "userid": "72e71cf8-18d8-11e4-98d6-5254004eff4f",
> "jobstatus": 0,
> "jobprocstatus": 0,
> "jobresultcode": 0,
> "created": "2014-08-07T10:51:43-0600",
> "jobid": "d17b557b-e36c-4f1e-badd-2013b1eb3af1"
> },
> {code}
> jobstatus,jobprocstataus, and jobresultcode are always 0.
> These appear to be internal threads to cloudstack and not related to any user
> submitted jobs.
> They do have an entry in the async_job table but provide no useful data in
> the listAsyncJobs API call.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
