[
https://issues.apache.org/jira/browse/CLOUDSTACK-9569?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15907843#comment-15907843
]
ASF subversion and git services commented on CLOUDSTACK-9569:
-------------------------------------------------------------
Commit 7b719c71fc15ce118fb3c2825790d615975eaefd in cloudstack's branch
refs/heads/4.9 from [~rajanik]
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=7b719c7 ]
Merge pull request #1856 from ustcweizhou/set-kvm-host-params
[4.9] CLOUDSTACK-9569: propagate global configuration
router.aggregation.command.each.timeout to KVM agentThe
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.
* pr/1856:
CLOUDSTACK-9569: propagate global configuration
router.aggregation.command.each.timeout to KVM agent
Signed-off-by: Rajani Karuturi <rajani.karut...@accelerite.com>
> 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.15#6346)
