Netvirt jobs are failing with Message "The given properties file path 'slave_addresses.txt' doesn't exist"
JamO Luhrsen
Srinivas, the problem seems to be with the instances from the cloud
provider not being SSH not responding on 10.30.170.24. Retrying in 10 seconds... SSH not responding on 10.30.170.21. Retrying in 10 seconds... Ping to 10.30.170.24 failed. Ping to 10.30.170.21 failed. SSH not responding on 10.30.170.24. Retrying in 10 seconds... SSH not responding on 10.30.170.21. Retrying in 10 seconds... Ping to 10.30.170.21 failed. Ping to 10.30.170.24 failed. SSH not responding on 10.30.170.24 after tries. Giving up. SSH not responding on 10.30.170.21 after tries. Giving up. Dumping console logs for c8a86fc6-8178-471f-9535-25b217a9d74d 10.30.170.21 Dumping console logs for 63bac154-9c0e-4c8a-9a69-b1322d2fb44d 10.30.170.24 Anyway, I don't think Anil is really reading ODL emails any more. Better to ask for help by opening an LFN ticket. Thanks, JamO On 8/5/20 4:14 AM,
srinivas.rachakonda@... wrote:
|
|
JamO Luhrsen
It's happening in other jobs as well. I filed the ticket:
JamO On 8/5/20 11:52 AM, Jamo Luhrsen wrote:
|
|
Anil Belur
Hello Srinivar, Jamo: Apologies for missing this thread. I've cleaned up the stale node and reverted the image that was causing this issue. Please rerun the jobs and update the JSD ticket if the issue persists. Cheers, Anil On Thu, Aug 6, 2020 at 7:57 AM Jamo Luhrsen <jluhrsen@...> wrote:
|
|
Srinivas <srinivas.rachakonda@...>
Hi Anil,
I am seeing VM ssh issues.
Could you please check the above link.
Also updated the same in JIRA.
Thanks, Srinivas +91-9243478719
From: Anil Belur <abelur@...>
Sent: 10 August 2020 09:45 To: Jamo Luhrsen <jluhrsen@...> Cc: srinivas.rachakonda@...; Karthikeyan Krishnan <karthikeyan.k@...>; P S Ravikanth <ravikanth.ps@...>; netvirt-dev <netvirt-dev@...>; integration-dev@... Subject: Re: Netvirt jobs are failing with Message "The given properties file path 'slave_addresses.txt' doesn't exist"
Hello Srinivar, Jamo:
Apologies for missing this thread. I've cleaned up the stale node and reverted the image that was causing this issue. Please rerun the jobs and update the JSD ticket if the issue persists.
Cheers, Anil
On Thu, Aug 6, 2020 at 7:57 AM Jamo Luhrsen <jluhrsen@...> wrote:
|
|