[
https://issues.apache.org/jira/browse/CLOUDSTACK-5843?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13868554#comment-13868554
]
ASF subversion and git services commented on CLOUDSTACK-5843:
-------------------------------------------------------------
Commit 9df5c18850b24db973c809fab3310224a823591f in branch refs/heads/4.3 from
[~mlsorensen]
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=9df5c18 ]
CLOUDSTACK-5843
For some reason the mgmt server is required to have access to the template
being registered in order to check its size against resource limits
during registration. This is bad, but worse, it's a sync call, so this
call can hang for up to the default HTTP connection timeout.
Reducing http timeout as a quick workaround, but this check needs to
1) be removed or 2) done later or 3)registerTemplate needs to be async
and 4) moved off the mgmt server (ssvm is the only thing that needs access to
template url).
> registering templates/isos should be either async or changed to non-blocking
> ----------------------------------------------------------------------------
>
> Key: CLOUDSTACK-5843
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5843
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: Management Server
> Affects Versions: 4.2.0, 4.3.0, 4.4.0
> Reporter: Marcus Sorensen
> Fix For: 4.4.0
>
>
> The call to register templates and isos does more than most sync calls do, it
> seems to talk to the ssvm and have it run commands that can potentially time
> out. I ran into this in a test system when we tried to register a template
> with a non-routable URL. The cloudstack API call just hung. I realize that
> there was a problem (ssvm could not reach the template host), but no sync
> call should do anything like this that would block.
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
