[
https://issues.apache.org/jira/browse/CLOUDSTACK-9569?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15861130#comment-15861130
]
ASF GitHub Bot commented on CLOUDSTACK-9569:
--------------------------------------------
Github user borisstoyanov commented on the issue:
https://github.com/apache/cloudstack/pull/1933
Testing has PASSED
There's a way to override the hardcoded timeout of 10 mins now by setting
the "router.aggregation.command.each.timeout" in the
"/etc/cloudstack/agent/agent.properties" file.
Testing steps:
Set the router.aggregation.command.each.timeout=1
Added a sleep of 15 seconds in the router_proxy.sh
Restarted the agent
Started a new VM with a new network
In the log the following observations were noted:
```
2017-01-20 12:04:05,787 DEBUG [kvm.resource.LibvirtComputingResource]
(agentRequest-Handler-2:null) Executing:
/usr/share/cloudstack-common/scripts/network/domr/router_proxy.sh vr_cfg.sh
169.254.3.57 -c /var/cache/cloud/VR-a20603a7-8e10-4378-96bb-7a2dbc7c6c0b.cfg
2017-01-20 12:04:06,792 WARN [kvm.resource.LibvirtComputingResource]
(agentRequest-Handler-2:null) Timed out:
/usr/share/cloudstack-common/scripts/network/domr/router_proxy.sh vr_cfg.sh
169.254.3.57 -c /var/cache/cloud/VR-a20603a7-8e10-4378-96bb-7a2dbc7c6c0b.cfg .
Output is:
2017-01-20 12:05:20,419 DEBUG [kvm.resource.LibvirtComputingResource]
(agentRequest-Handler-1:null) Executing:
/usr/share/cloudstack-common/scripts/network/domr/router_proxy.sh vr_cfg.sh
169.254.0.41 -c /var/cache/cloud/VR-090cae6a-f07d-40bb-9f19-809ccdcca16b.cfg
2017-01-20 12:05:21,423 WARN [kvm.resource.LibvirtComputingResource]
(agentRequest-Handler-1:null) Timed out:
/usr/share/cloudstack-common/scripts/network/domr/router_proxy.sh vr_cfg.sh
169.254.0.41 -c /var/cache/cloud/VR-090cae6a-f07d-40bb-9f19-809ccdcca16b.cfg .
Output is:
2017-01-20 12:06:33,620 DEBUG [kvm.resource.LibvirtComputingResource]
(agentRequest-Handler-1:null) Executing:
/usr/share/cloudstack-common/scripts/network/domr/router_proxy.sh vr_cfg.sh
169.254.2.33 -c /var/cache/cloud/VR-63f52dbd-b710-4e57-a21b-1f4bcd146ec3.cfg
2017-01-20 12:06:34,624 WARN [kvm.resource.LibvirtComputingResource]
(agentRequest-Handler-1:null) Timed out:
/usr/share/cloudstack-common/scripts/network/domr/router_proxy.sh vr_cfg.sh
169.254.2.33 -c /var/cache/cloud/VR-63f52dbd-b710-4e57-a21b-1f4bcd146ec3.cfg .
Output is:
```
VR Failed to start with a Message "Unable to start a VM due to insufficient
capacity"
I think we could add a log message saying that it timed out in the agent
log, because now it does not leave any clue where the time out is.
> 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)
