Hi Girish, While selecting the delay I suggest the following.
In general check the time taken for the router boot up. Take the max interval as 10 times of boot up time. Repeat the ssh for each boot up interval. Thanks, Jayapal On 30-Sep-2013, at 1:38 PM, Girish Shilamkar <gir...@clogeny.com> wrote: > Marcus, > > I guess it no longer applies to even KVM . I have seen the router in running > state and yet fails to accept > ssh connection. > > Santhosh, > > Adding random delay is what I am trying to avoid or at least minimise. Thanks > for the suggestions. > > Regards, > Girish > > On 30-Sep-2013, at 12:18 PM, Marcus Sorensen <shadow...@gmail.com> wrote: > >> In the past, with KVM, the agent doesn't show the router as running until >> it can ssh to it. You can watch the agent poll if it is debug logging. Does >> this issue not apply to KVM, or is it a regression? >> On Sep 29, 2013 11:38 PM, "Girish Shilamkar" <gir...@clogeny.com> wrote: >> >>> Hello, >>> >>> Egress rules tests rely on accessing virtual router VR after creating a >>> network. I have often seen that VR is not immediately accessible. >>> A ssh to VR fails, I think it takes a while for the network to come up and >>> VR can be ssh'd. This happens even though the VR is in "Running" >>> state. >>> So I added a delay before trying to ssh VR. I was wondering what is the >>> right amount of delay here. I did not find a param in global settings >>> which can be used as wait time. >>> >>> Please advise. >>> >>> Regards, >>> Girish >>> >>> >
