• Icon: Task Task
    • Resolution: Cannot Reproduce
    • Icon: Major Major
    • core, packaging
    • None

      When running the latest upgrade, I received the invalid keys message.  Upon looking up the issue, I found in the change log that I needed to update the public keys, which I did with no issues.  Then I re-ran the upgrade (yum upgrade jenkins) and did not receive any errors.  The Jenkins appeared to be starting up normally, but then I noticed that it was acting like I had never had Jenkins installed.  It was performing what looked like an initial install, which seemed even more confirmed when it asked me for the initial Administrator password.  After finishing starting up, I had no jobs any more, the configuration seemed to be completely gone.  Previously installed plugins were no longer there and jobs / configurations were all gone.  In looking into the directory structure on the OS, I still see my jobs defined, etc.   There doesn't seem to be any way of importing these jobs back in either.    Wish I could get my configuration back, or at a minimum, get my jobs imported back in.  I have several other Jenkins servers, but I do not want to upgrade any other servers for fear of loosing those configurations as well.

          [JENKINS-63240] Configuration is gone after latest upgrade

          Oleg Nenashev added a comment -

          Hi. I have tried this update scenario on CentOS, and for me it worked well. Any chance you have had any customizations in init files and sysconfig? 

           

          CC olblak-admin markewaite olivergondza

          Oleg Nenashev added a comment - Hi. I have tried this update scenario on CentOS, and for me it worked well. Any chance you have had any customizations in init files and sysconfig?    CC olblak-admin markewaite   olivergondza

          Chad Utter added a comment -

          Yes, that's where my instance is running, CentOS 7.8.  My other instances are also 7.x as well, but I haven't upgraded any of them to this latest versions.  I have been able to upgrade the instances in the past without issue, so this once surprised me when it removed all of my configurations and jobs.  As for startup files, I don't have anything that I would consider "special" or different from the stock install.  This particular instance was only using the docker plugin to run a docker python image, pylint and some reporting plugins for a python build.

          Chad Utter added a comment - Yes, that's where my instance is running, CentOS 7.8.  My other instances are also 7.x as well, but I haven't upgraded any of them to this latest versions.  I have been able to upgrade the instances in the past without issue, so this once surprised me when it removed all of my configurations and jobs.  As for startup files, I don't have anything that I would consider "special" or different from the stock install.  This particular instance was only using the docker plugin to run a docker python image, pylint and some reporting plugins for a python build.

          cautter, here are several troubleshooting suggestions:

          • Are the data still in JENKINS_HOME (likely /var/lib/jenkins) directory?
            • Is it using the same JENKINS_HOME it was before?
          • What is the exact command sequence you have run to upgrade?
          • Can you inspect and attach /var/log/yum.log?

          Oliver Gondža added a comment - cautter , here are several troubleshooting suggestions: Are the data still in JENKINS_HOME (likely /var/lib/jenkins ) directory? Is it using the same JENKINS_HOME it was before? What is the exact command sequence you have run to upgrade? Can you inspect and attach /var/log/yum.log ?

          Mark Waite added a comment -

          After 18 months without a response, closing as "Cannot reproduce"

          Mark Waite added a comment - After 18 months without a response, closing as "Cannot reproduce"

            Unassigned Unassigned
            cautter Chad Utter
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: