Re: [vpp-dev] [FD.io Helpdesk #74794] Jenkins.fd.io network issues - CSIT-1904 rls showstopper [CRITICAL]

2019-05-02 Thread Maciek Konstantynowicz via RT
Hello, CRITICAL ISSUE: ALL CSIT PERFORMANCE TESTING JOBS ARE EFFECTED. 1904 RLS SHOWSTOPPER. This is now a critical issue as all CSIT performance testing jobs are failing, preventing FD.io CSIT project to complete the CSIT-1904 release. This ticket #74794, is related to the same

Re: [vpp-dev] [FD.io Helpdesk #74794] Jenkins.fd.io network issues - CSIT-1904 rls showstopper [CRITICAL]

2019-05-02 Thread Maciek Konstantynowicz via RT
Hello, CRITICAL ISSUE: ALL CSIT PERFORMANCE TESTING JOBS ARE EFFECTED. 1904 RLS SHOWSTOPPER. This is now a critical issue as all CSIT performance testing jobs are failing, preventing FD.io CSIT project to complete the CSIT-1904 release. This ticket #74794, is related to the same

Re: [vpp-dev] [csit-dev] [FD.io Helpdesk #41921] connection interruptiones between jenkins executor and VIRL servers

2017-06-28 Thread Maciek Konstantynowicz via RT
Ah well, I assumed the default gateway router is running IP routing stack compliant with RFC791 and associated best practices of selecting best routes for forwarding. If this is not the case, then I would like the administrator of the aforementioned default gateway router to confirm the implemen

Re: [vpp-dev] [csit-dev] [FD.io Helpdesk #41921] connection interruptiones between jenkins executor and VIRL servers

2017-06-28 Thread Maciek Konstantynowicz via RT
Anton and Team, The continued interruptions of IP connectivity to/from VIRL server simulations on the management subnet have been impacting both CSIT and VPP project operations. We decided to temporarily remove VPP VIRL based verify jobs, job/vpp-csit-verify-virl-master/, from both per vpp patc

Re: [vpp-dev] [csit-dev] [FD.io Helpdesk #41298] Jobs are not triggered from gerrit

2017-05-31 Thread Maciek Konstantynowicz via RT
it seems to be working now. many thanks Vanessa and team ! -Maciek > On 31 May 2017, at 21:28, Vanessa Valderrama via RT > wrote: > > Restarting the plugin appears to have resolved this issue. I've run several > rechecks that all triggered properly. Since this issue appeared to be > resolv