Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-63962

Getting OOPS Message after login to Jenkins (Happening after upgrading jenkins to 2.249.1 and plugins)

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Major Major
    • core
    • None
    • Production

      Hi Team ,

      After Upgrading to Jenkins 2.249.1 and upgrade all the plugins we are facing the issue post login to jenkins with OOPS message ,resource can't be reach.

      also this is happening to non-admin user only .

      it is the show stopper for us as many team are using.Please see this on high priority.

      I have attached screenshot for the error and the plugin list also that we have updated and have installed.

      Regards

      Arun

       

          [JENKINS-63962] Getting OOPS Message after login to Jenkins (Happening after upgrading jenkins to 2.249.1 and plugins)

          HI Oleg,

          as far as I know ,we have read permission for the jobs we are getting the error . so this should not be the case . right?

           

          Regards

          Arun

          Arunpreet Singh added a comment - HI Oleg, as far as I know ,we have read permission for the jobs we are getting the error . so this should not be the case . right?   Regards Arun

          HI Team,

          Any update on this Issue?

          Regards

          Arun

          Arunpreet Singh added a comment - HI Team, Any update on this Issue? Regards Arun

          Hi Team oleg_nenashev,

          WE have observe that its happening only for pipeline job only.if some one doesn't have permission to see that pipeline job and if that pipeline. job is getting. executed while that user(user who doesn't have the permission to see this job) logged in then only we are getting this issue.

          can you please guide us on this?

          Regards

          Arun

          Arunpreet Singh added a comment - Hi Team oleg_nenashev , WE have observe that its happening only for pipeline job only.if some one doesn't have permission to see that pipeline job and if that pipeline. job is getting. executed while that user(user who doesn't have the permission to see this job) logged in then only we are getting this issue. can you please guide us on this? Regards Arun

          Oleg Nenashev added a comment -

          As stated before it is likely a duplicate of JENKINS-63868. You described exactly a root cause scenario for it arunpreet_singh . Please verify the fix linked from the referenced issue

          Oleg Nenashev added a comment - As stated before it is likely a duplicate of JENKINS-63868 . You described exactly a root cause scenario for it arunpreet_singh . Please verify the fix linked from the referenced issue

          Hi oleg_nenashev,

          not sure that fix work because we are not using Discover on any job alone , what I found after testing is that its workflow-durable-task-step-plugin issue with version 2.36.

          I downgraded that and it fix the issue.

          I am still doing some more. testing and will update 

          Regards

          Arun

          Arunpreet Singh added a comment - Hi oleg_nenashev , not sure that fix work because we are not using Discover on any job alone , what I found after testing is that its workflow-durable-task-step-plugin issue with version 2.36. I downgraded that and it fix the issue. I am still doing some more. testing and will update  Regards Arun

          Oleg Nenashev added a comment - - edited

          Ack. It will need more investigation if the Discover is not set on any Job or Folder (just jobs are not enough here). Taking the stacktrace, JENKINS-63868 should fix the issue anyway, it should prevent any AccessDenied exceptions

          Oleg Nenashev added a comment - - edited Ack. It will need more investigation if the Discover is not set on any Job or Folder (just jobs are not enough here). Taking the stacktrace,  JENKINS-63868  should fix the issue anyway, it should prevent any AccessDenied exceptions

          Oleg Nenashev added a comment -

          Please try JENKINS-63868 with the fix

          Oleg Nenashev added a comment - Please try  JENKINS-63868  with the fix

          Sven Scheil added a comment - - edited

          We have the same issue and it is a blocker for our developers. I've read also JENKINS-63868 , but don't be sure how to work around it. Do I have to rollback to a certain Jenkins version or do I only have to rollback the workflow-durable-task-step-plugin to a certain version?

          Any help is appreciated.

          Sven Scheil added a comment - - edited We have the same issue and it is a blocker for our developers. I've read also  JENKINS-63868  , but don't be sure how to work around it. Do I have to rollback to a certain Jenkins version or do I only have to rollback the workflow-durable-task-step-plugin to a certain version? Any help is appreciated.

          svc,

          Reverting the version to 2.35 for plugin workflow-durable-task-step-plugin will resolve .

          Thanks 

          AArun

          Arunpreet Singh added a comment - svc , Reverting the version to 2.35 for plugin workflow-durable-task-step-plugin will resolve . Thanks  AArun

          Sven Scheil added a comment -

          arunpreet_singh THX. That worked.

          Sven Scheil added a comment - arunpreet_singh THX. That worked.

            naveenboni Naveen Boni
            arunpreet_singh Arunpreet Singh
            Votes:
            4 Vote for this issue
            Watchers:
            6 Start watching this issue

              Created:
              Updated: