On Fri, Jun 4, 2021 at 2:16 PM Fabian Arrotin <arrfab at centos.org> wrote: > > On 04/06/2021 08:53, Anjan Nath wrote: > > Hi, We are seeing jobs[0] failing with some JNLP error from yesterday > > (console snip added below), not sure if this is known already or maybe > > related to the upgrade done? > > > > ``` > > 06:42:21 Also: hudson.remoting.Channel$CallSiteStackTrace: Remote > > call to JNLP4-connect connection from > > slave02.ci.centos.org/172.19.0.15:57126 > > 06:42:21 at hudson.remoting.Channel.attachCallSiteStackTrace(Channel.java:1800) > > 06:42:21 at hudson.remoting.UserRequest$ExceptionResponse.retrieve(UserRequest.java:356) > > 06:42:21 at hudson.remoting.Channel.call(Channel.java:1001) > > 06:42:21 at hudson.FilePath.act(FilePath.java:1158) > > 06:42:21 at hudson.FilePath.act(FilePath.java:1147) > > 06:42:21 at org.jenkinsci.plugins.gitclient.Git.getClient(Git.java:121) > > ``` > > [0] https://ci.centos.org/job/codeready-crc-pr/3612/console > > > > It seems the Jenkins itself (on https://ci.centos.org) was updated but > *not* the jenkins agents, which caused the issue, so have just updated > and restarted the agents. > > Can you verify ? > Thanks Arrafb, after updating and restarting agents, jobs are no longer seeing the JNLP Traceback. > PS : next time create ticket on https://pagure.io/centos-infra/issues > > -- > Fabian Arrotin > The CentOS Project | https://www.centos.org > gpg key: 17F3B7A1 | twitter: @arrfab > _______________________________________________ > CI-users mailing list > CI-users at centos.org > https://lists.centos.org/mailman/listinfo/ci-users > Thanks and Regards Yatin Karel