add CLOUDSTACK-7595 link

This closes #18

Signed-off-by: Rohit Yadav <ro...@scaleninja.com>


Project: http://git-wip-us.apache.org/repos/asf/cloudstack-docs-rn/repo
Commit: 
http://git-wip-us.apache.org/repos/asf/cloudstack-docs-rn/commit/51534d2f
Tree: http://git-wip-us.apache.org/repos/asf/cloudstack-docs-rn/tree/51534d2f
Diff: http://git-wip-us.apache.org/repos/asf/cloudstack-docs-rn/diff/51534d2f

Branch: refs/heads/4.4
Commit: 51534d2fc9f050aba8e22a2f2ac3a5caa6be94c5
Parents: d4777b6
Author: Remi Bergsma <git...@remi.nl>
Authored: Thu Mar 12 11:00:07 2015 +0100
Committer: Rohit Yadav <ro...@scaleninja.com>
Committed: Thu Mar 12 15:57:35 2015 +0530

----------------------------------------------------------------------
 source/fixed_issues.rst | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)
----------------------------------------------------------------------


http://git-wip-us.apache.org/repos/asf/cloudstack-docs-rn/blob/51534d2f/source/fixed_issues.rst
----------------------------------------------------------------------
diff --git a/source/fixed_issues.rst b/source/fixed_issues.rst
index 4a1b7bf..5e3c4bc 100644
--- a/source/fixed_issues.rst
+++ b/source/fixed_issues.rst
@@ -80,4 +80,4 @@ Bug ID                                                        
              Desc
 
 Note: Job timeouts are shorter than before
 ----------------------------------------
-Please be aware that in 4.4 a bug is fixed (CLOUDSTACK-7595) that makes sure 
global settings 'job.cancel.threshold.minutes' and 'job.expire.minutes' are 
defined in minutes as they are supposed to be. Before, they were accidentally 
60x bigger than configured. This means previous versions had a much higher 
timeout. You might hit this timeout when migrating large disks or making big 
snapshots, etc.
+Please be aware that in 4.4 a bug is fixed (`CLOUDSTACK-7595 
<https://issues.apache.org/jira/browse/CLOUDSTACK-7595>`_) that makes sure 
global settings 'job.cancel.threshold.minutes' and 'job.expire.minutes' are 
defined in minutes as they are supposed to be. Before, they were accidentally 
60x bigger than configured. This means previous versions had a much higher 
timeout. You might hit this timeout when migrating large disks or making big 
snapshots, etc.

Reply via email to