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

Upgrade 1.x to 2.x: upgrade wizard disappears when auto refresh is enabled

    • Icon: Bug Bug
    • Resolution: Won't Fix
    • Icon: Minor Minor
    • core
    • None
    • Upgrade from 1.651.3 to 2.32.3
    • 2.220 and 2.235.1 remove the auto refresh

      Short version

      When auto refresh of the Jenkins GUI is enabled prior to starting a 1.6 -> 2.x upgrade, the upgrade wizard closes after a few seconds due to the auto refresh kicking in.

       

      Versions/software used

      • Jenkins 1.6:
        docker run -p 8080:8080 -p 50000:50000 -v /Users/bertjan/jenkins/home:/var/jenkins_home jenkins:1.651.3

       

      • Jenkins 2.3:
        docker run -p 8080:8080 -p 50000:50000 -v /Users/bertjan/jenkins/home:/var/jenkins_home jenkins:2.32.3

      Reproduction path

      • Install Jenkins 1.6
      • Stop the 1.6 instance, start a Jenkins 2.3 instance and point it to the same homedir used for the 1.6 instance
      • When the Jenkins 2.3 instance boots, don't log in and start the upgrade wizard just yet
      • First, make sure that auto refresh is enabled (by clicking "ENABLE AUTO REFRESH" in the top right corner)
      • Click 'Upgrade now' to start the upgrade wizard'
      • Click 'Continue'. The upgrade starts.
      • Wait a bit for the autorefresh to kick in. This closes the upgrade wizard dialog window.

      The upgrade does continue (looking at the logs in my terminal) but there's no way of viewing its progress in the GUI.

      This doesn't happen when auto refresh isn't enabled.

       

      Additional info

      I marked this issue with priority "major" because this can have quite a negative influence on the trust that new 2.x users have in the upgrade. Imagine finally gaining enough courage for taking the step to upgrade your mission-critical installation to 2.x, only to see the upgrade wizard disappear after a few seconds and being completely in the blue whether the upgrade succeeded or failed. I can hear managers shouting "rollback! rollback!" already

      I think it would be alright to just disable auto refresh before the upgrade wizard starts. If the user really wants auto refresh, he/she will enable it again after the upgrade.

          [JENKINS-43111] Upgrade 1.x to 2.x: upgrade wizard disappears when auto refresh is enabled

          Bert Jan Schrijver created issue -
          Bert Jan Schrijver made changes -
          Description Original: *Short version*

          When auto refresh of the Jenkins GUI is enabled prior to starting a 1.6 -> 2.x upgrade, the upgrade wizard closes after a few seconds due to the auto refresh kicking in.

           

          *Versions/software used*
           * Jenkins 1.6:
          {{docker run -p 8080:8080 -p 50000:50000 -v /Users/bertjan/jenkins/home:/var/jenkins_home jenkins:1.651.3}}

           
           * Jenkins 2.3:
          {{docker run -p 8080:8080 -p 50000:50000 -v /Users/bertjan/jenkins/home:/var/jenkins_home jenkins:2.32.3}}


          *Reproduction path*
           * Install Jenkins 1.6
           * Stop the 1.6 instance, start a Jenkins 2.3 instance and point it to the same homedir used for the 1.6 instance
           * When the Jenkins 2.3 instance boots, don't log in and start the upgrade wizard just yet
           * First, make sure that auto refresh is enabled (by clicking "ENABLE AUTO REFRESH" in the top right corner)
           * Click 'Upgrade now' to start the upgrade wizard'
           * Click 'Continue'. The upgrade starts.
           * Wait a bit for the autorefresh to kick in. This closes the upgrade wizard dialog window.

          The upgrade does continue (looking at the logs in my terminal) but there's no way of viewing its progress in the GUI.

          This doesn't happen when auto refresh isn't enabled.

          Priority "major" because this can have quite a negative influence on the trust of new 2.x users. Imagine finally taking the step to upgrade your mission-critical installation to 2.x, only to see the upgrade wizard disappear after a few seconds and being completely in the blue whether the upgrade succeeded or failed.

          I think it would be alright to just disable auto refresh before the upgrade wizard starts. If the user really wants auto refresh, he/she will enable it again after the upgrade.
          New: *Short version*

          When auto refresh of the Jenkins GUI is enabled prior to starting a 1.6 -> 2.x upgrade, the upgrade wizard closes after a few seconds due to the auto refresh kicking in.

           

          *Versions/software used*
           * Jenkins 1.6:
           {{docker run -p 8080:8080 -p 50000:50000 -v /Users/bertjan/jenkins/home:/var/jenkins_home jenkins:1.651.3}}

           
           * Jenkins 2.3:
           {{docker run -p 8080:8080 -p 50000:50000 -v /Users/bertjan/jenkins/home:/var/jenkins_home jenkins:2.32.3}}

          *Reproduction path*
           * Install Jenkins 1.6
           * Stop the 1.6 instance, start a Jenkins 2.3 instance and point it to the same homedir used for the 1.6 instance
           * When the Jenkins 2.3 instance boots, don't log in and start the upgrade wizard just yet
           * First, make sure that auto refresh is enabled (by clicking "ENABLE AUTO REFRESH" in the top right corner)
           * Click 'Upgrade now' to start the upgrade wizard'
           * Click 'Continue'. The upgrade starts.
           * Wait a bit for the autorefresh to kick in. This closes the upgrade wizard dialog window.

          The upgrade does continue (looking at the logs in my terminal) but there's no way of viewing its progress in the GUI.

          This doesn't happen when auto refresh isn't enabled.

           

          *Additional info*

          I marked this issue with priority "major" because this can have quite a negative influence on the trust that new 2.x users have in the upgrade. Imagine finally gaining enough courage for taking the step to upgrade your mission-critical installation to 2.x, only to see the upgrade wizard disappear after a few seconds and being completely in the blue whether the upgrade succeeded or failed. I can hear managers shouting "rollback! rollback!" already ;)

          I think it would be alright to just disable auto refresh before the upgrade wizard starts. If the user really wants auto refresh, he/she will enable it again after the upgrade.
          Oleg Nenashev made changes -
          Assignee New: Keith Zantow [ kzantow ]
          Keith Zantow made changes -
          Priority Original: Major [ 3 ] New: Minor [ 4 ]
          Bert Jan Schrijver made changes -
          Attachment New: audience.jpg [ 36796 ]
          Daniel Beck made changes -
          Link New: This issue is related to JENKINS-19828 [ JENKINS-19828 ]
          Mark Waite made changes -
          Released As New: 2.220 and 2.235.1 remove the auto refresh
          Resolution New: Won't Fix [ 2 ]
          Status Original: Open [ 1 ] New: Resolved [ 5 ]

            kzantow Keith Zantow
            bertjan Bert Jan Schrijver
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: