[
https://issues.apache.org/jira/browse/CLOUDSTACK-9569?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15769617#comment-15769617
]
ASF GitHub Bot commented on CLOUDSTACK-9569:
--------------------------------------------
GitHub user ustcweizhou opened a pull request:
https://github.com/apache/cloudstack/pull/1856
CLOUDSTACK-9569: propagate global configuration
router.aggregation.command.each.timeout to KVM agent
The router.aggregation.command.each.timeout in global configuration is only
applied on new created KVM host.
For existing KVM host, changing the value will not be effective.
We need to propagate the configuration to existing host when
cloudstack-agent is connected.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/ustcweizhou/cloudstack set-kvm-host-params
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/cloudstack/pull/1856.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #1856
----
commit ec5ab8dc196227bc728d5667090aa98fe8baf651
Author: Wei Zhou <[email protected]>
Date: 2016-12-22T09:14:36Z
CLOUDSTACK-9569: propagate global configuration
router.aggregation.command.each.timeout to KVM agent
----
> VR on shared network not starting on KVM
> ----------------------------------------
>
> Key: CLOUDSTACK-9569
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9569
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: Network Controller
> Affects Versions: 4.9.0
> Reporter: John Burwell
> Priority: Critical
> Fix For: 4.9.2.0, 4.10.1.0, 4.11.0.0
>
> Attachments: cloud.log
>
>
> A VR for a shared network on KVM fails to complete startup with the following
> behavior:
> # VR starts on KVM
> # Agent pings VR
> # Increase timeout from from 120 seconds to 1200 seconds
> # API configuration starts
> The Management Server reports that the command times out. Please see the
> attached {cloud.log} which depicts the activity of the VR through the
> timeout. This failure does not occur on VMware.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
