[
https://issues.apache.org/jira/browse/CLOUDSTACK-8949?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14957970#comment-14957970
]
Ryan Farrington commented on CLOUDSTACK-8949:
---------------------------------------------
[~dahn],
I am just a lowly end user and was working through an issue with Rafael
Weingärtner in the users mailing list when he asked that I create a jira ticket
to track this. Is it s bug? sure? We are seeing multiple timeout values not
being followed or superseding each other. If that is not a bug let me know
what type it should be and I will happily make the modification.
> Job timeout caused by improper/inconsistent application of wait parameters
> --------------------------------------------------------------------------
>
> Key: CLOUDSTACK-8949
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-8949
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: Hypervisor Controller
> Affects Versions: 4.3.0
> Environment: XenServer 6.2
> Reporter: Ryan Farrington
> Priority: Minor
>
> when creating a "MigrateVolumeCommand" a timeout should be set, this way the
> ACS would not use the default value of parameter "wait". That timeout value
> should be the same as the one used on CitrixResourceBase and its children to
> control the migration of volumes.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
