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

Config File Provider NPE on upgrade to 3.6.2

    XMLWordPrintable

Details

    • Bug
    • Status: Open (View Workflow)
    • Major
    • Resolution: Unresolved
    • None
    • jenkins/jenkins:lts image (2.176.1) on CentOS 7 host
      Config File Provider 3.6.2

    Description

      When upgrading from 3.0 to 3.6.2 there's an NPE when loading a GitHub Organization:

      Jul 16, 2019 10:03:29 AM jenkins.InitReactorRunner$1 onTaskFailed
      SEVERE: Failed Loading item csullivannet
      java.lang.NullPointerException
      	at jenkins.branch.OrganizationFolder.onLoad(OrganizationFolder.java:214)
      	at hudson.model.Items.load(Items.java:373)
      	at jenkins.model.Jenkins$14.run(Jenkins.java:3162)
      	at org.jvnet.hudson.reactor.TaskGraphBuilder$TaskImpl.run(TaskGraphBuilder.java:169)
      	at org.jvnet.hudson.reactor.Reactor.runTask(Reactor.java:296)
      	at jenkins.model.Jenkins$5.runTask(Jenkins.java:1091)
      	at org.jvnet.hudson.reactor.Reactor$2.run(Reactor.java:214)
      	at org.jvnet.hudson.reactor.Reactor$Node.run(Reactor.java:117)
      	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
      	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
      	at java.lang.Thread.run(Thread.java:748)
      

      Attachments

        Activity

          csullivannet Christopher Sullivan created issue -
          oleg_nenashev Oleg Nenashev added a comment -

          It does not look like Config File provider is involvved here. Any evidence?

           

          oleg_nenashev Oleg Nenashev added a comment - It does not look like Config File provider is involvved here. Any evidence?  
          csullivannet Christopher Sullivan added a comment - - edited

          All of my plugins are currently up to date, except for Config File Provider which is on 3.0. When I update Config File Provider to 3.6.2, this is the exception I get.

          csullivannet Christopher Sullivan added a comment - - edited All of my plugins are currently up to date, except for Config File Provider which is on 3.0 . When I update Config File Provider to 3.6.2 , this is the exception I get.
          oleg_nenashev Oleg Nenashev added a comment -

          https://github.com/jenkinsci/branch-api-plugin/blame/master/src/main/java/jenkins/branch/OrganizationFolder.java . Looks like "navigators" field is null due to whatever reason. 

           

          csullivannet any chance you use Configuration-as-code plugin or JobDSL? If so, please provide the config

          oleg_nenashev Oleg Nenashev added a comment - https://github.com/jenkinsci/branch-api-plugin/blame/master/src/main/java/jenkins/branch/OrganizationFolder.java  . Looks like "navigators" field is null due to whatever reason.    csullivannet any chance you use Configuration-as-code plugin or JobDSL? If so, please provide the config

          I'm not using CasC or DSL for this job, sorry.

          csullivannet Christopher Sullivan added a comment - I'm not using CasC or DSL for this job, sorry.

          Does the config.xml of the job help?

          csullivannet Christopher Sullivan added a comment - Does the config.xml of the job help?
          csullivannet Christopher Sullivan added a comment - - edited

          I tried upgrading Jenkins to 2.185 and the issue persists.

          csullivannet Christopher Sullivan added a comment - - edited I tried upgrading Jenkins to 2.185 and the issue persists.
          nfalco Nikolas Falco added a comment -

          I have version 3.7.0 and latest version of folder plugin and I did not get this exception

          nfalco Nikolas Falco added a comment - I have version 3.7.0 and latest version of folder plugin and I did not get this exception
          imod Dominik Bartholdi made changes -
          Field Original Value New Value
          Assignee Dominik Bartholdi [ domi ] Ramon Leon [ mramonleon ]

          We're still encountering this issue on 2.289.1. Upgrading from 3.0.0 -> 3.7.0, and upgrading from 3.0.0 -> 3.8.0 both produce this error.

          csullivannet Christopher Sullivan added a comment - We're still encountering this issue on 2.289.1 . Upgrading from 3.0.0 -> 3.7.0 , and upgrading from 3.0.0 -> 3.8.0 both produce this error.
          mramonleon Ramon Leon added a comment -

          csullivannetcould you provide some reproduction steps to let us be able to work on this issue. We can't figure out how to find the issue without any other hint. Maybe a job configured the same you can provide us with the same issue or so? Thanks

          mramonleon Ramon Leon added a comment - csullivannet could you provide some reproduction steps to let us be able to work on this issue. We can't figure out how to find the issue without any other hint. Maybe a job configured the same you can provide us with the same issue or so? Thanks

          People

            mramonleon Ramon Leon
            csullivannet Christopher Sullivan
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated: