cloudstack-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Özhan Rüzgar Karaman (JIRA) <>
Subject [jira] [Commented] (CLOUDSTACK-9503) The router script times out resulting in failure of deployment
Date Tue, 01 Nov 2016 06:04:58 GMT


Özhan Rüzgar Karaman commented on CLOUDSTACK-9503:

First for all this is an important bug so thanks for fixing for this bugfix [~aprateek] [~jburwell]
, i am also following a smilar bug CLOUDSTACK-9319 which was accepted and will be available
for upcoming 4.10 release. Your solution has wide coverage area for different host so yours
are better, i write this comment just for the information and thanks for the great work &

> The router script times out resulting in failure of deployment
> --------------------------------------------------------------
>                 Key: CLOUDSTACK-9503
>                 URL:
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the default.) 
>          Components: Virtual Router
>    Affects Versions: 4.9.0
>         Environment: KVM, Xen
>            Reporter: Abhinandan Prateek
>            Assignee: Abhinandan Prateek
>             Fix For:
> When starting the virtual router in a shared network in advance zone the scripts on router
time out. This happen as there are several sub-commands that are consolidated in a single
command. The default timeout of 2 minutes is short.
> 2016-09-09 00:06:25,016 ERROR [c.c.n.r.VirtualNetworkApplianceManagerImpl] (Work-Job-Executor-110:ctx-e8089ec7
job-5135/job-5137 ctx-c3a8da18) (logid:8aedea66) process hasn't exited
> 2016-09-09 00:06:25,016 WARN [c.c.n.r.VirtualNetworkApplianceManagerImpl] (Work-Job-Executor-110:ctx-e8089ec7
job-5135/job-5137 ctx-c3a8da18) (logid:8aedea66) Command: failed
while starting virtual router
> 2016-09-09 00:06:25,016 INFO [c.c.v.VirtualMachineManagerImpl] (Work-Job-Executor-110:ctx-e8089ec7
job-5135/job-5137 ctx-c3a8da18) (logid:8aedea66) The guru did not like the answers so stopping
> —

This message was sent by Atlassian JIRA

View raw message