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

Artifacts and workspace not accessible after upgrade from LTS 2.138 to 2.150.2+ (IIS reverse proxy)

    • Jenkins 2.168

      Using IIS reverse proxy, on LTS 2.138 artifacts and workspace were accessible through web UI as expected.  Windows Server 2016 using MSFT docker container, OpenJDK8 or 11 (currently 8) to load jenkins.war file on container start.

      After upgrade to LTS 2.150.2, or mainstream 2.164, artifacts are no longer visible on the jobs through the web UI, and accessing job workspaces present a 403 error.

      HTTP ERROR 403

      Problem accessing /job/<job_name_redacted>/ws/. Reason:

      Trying to access a file outside of the directory, target:

       


      Powered by Jetty:// 9.4.z-SNAPSHOT

       

      Attempted upgrade of container to OpenJDK 11, same errors occur.

      Job artifacts are created and present on local file system.  Workspace is created and present on local file system.  Job will build project, just won't present the results/workspace through the UI.

      Downgrading back to LTS 2.138 and the job artifacts and workspaces are visible/accessible with same IIS configuration.

      IIS reverse proxy reference:  https://wiki.jenkins.io/display/JENKINS/Running+Jenkins+behind+IIS (instead of localhost and host file, used container IP address directly).  Tested as working in 2.138, fails on 2.150.2+, works correctly when reverted to 2.138.

          [JENKINS-56114] Artifacts and workspace not accessible after upgrade from LTS 2.138 to 2.150.2+ (IIS reverse proxy)

          Jeremy Kam created issue -
          Jeremy Kam made changes -
          Summary Original: Artifacts and workspace not accessible after upgrade from 2.138 to 2.150.2+ New: Artifacts and workspace not accessible after upgrade from 2.138 to 2.150.2+ (IIS reverse proxy)
          Jeremy Kam made changes -
          Description Original: Using IIS reverse proxy, on LTS 2.138 artifacts and workspace were accessible as expected.

          After upgrade to LTS 2.150.2, or mainstream 2.164, artifacts are no longer visible on the jobs through the web UI, and accessing job workspaces present a 403 error.

          "Problem accessing /job/<jobname>/ws/. Reason:

          Trying to access a file outside of the directory, target:"

          Attempted upgrade of container to OpenJDK 11, same errors occur.

          Job artifacts are created and present on local file system.  Workspace is created and present on local file system.
          New: Using IIS reverse proxy, on LTS 2.138 artifacts and workspace were accessible as expected.

          After upgrade to LTS 2.150.2, or mainstream 2.164, artifacts are no longer visible on the jobs through the web UI, and accessing job workspaces present a 403 error.

          "Problem accessing /job/<jobname>/ws/. Reason:

          Trying to access a file outside of the directory, target:"

          Attempted upgrade of container to OpenJDK 11, same errors occur.

          Job artifacts are created and present on local file system.  Workspace is created and present on local file system.

          Downgrading back to LTS 2.138 and the job artifacts and workspaces are visible/accessible with same IIS configuration.
          Jeremy Kam made changes -
          Description Original: Using IIS reverse proxy, on LTS 2.138 artifacts and workspace were accessible as expected.

          After upgrade to LTS 2.150.2, or mainstream 2.164, artifacts are no longer visible on the jobs through the web UI, and accessing job workspaces present a 403 error.

          "Problem accessing /job/<jobname>/ws/. Reason:

          Trying to access a file outside of the directory, target:"

          Attempted upgrade of container to OpenJDK 11, same errors occur.

          Job artifacts are created and present on local file system.  Workspace is created and present on local file system.

          Downgrading back to LTS 2.138 and the job artifacts and workspaces are visible/accessible with same IIS configuration.
          New: Using IIS reverse proxy, on LTS 2.138 artifacts and workspace were accessible through web UI as expected.  Windows Server 2016 using MSFT docker container, OpenJDK8 or 11 (currently 8) to load jenkins.war file on container start.

          After upgrade to LTS 2.150.2, or mainstream 2.164, artifacts are no longer visible on the jobs through the web UI, and accessing job workspaces present a 403 error.

          "Problem accessing /job/<jobname>/ws/. Reason:

          Trying to access a file outside of the directory, target:"

          Attempted upgrade of container to OpenJDK 11, same errors occur.

          Job artifacts are created and present on local file system.  Workspace is created and present on local file system.

          Downgrading back to LTS 2.138 and the job artifacts and workspaces are visible/accessible with same IIS configuration.
          Jeremy Kam made changes -
          Description Original: Using IIS reverse proxy, on LTS 2.138 artifacts and workspace were accessible through web UI as expected.  Windows Server 2016 using MSFT docker container, OpenJDK8 or 11 (currently 8) to load jenkins.war file on container start.

          After upgrade to LTS 2.150.2, or mainstream 2.164, artifacts are no longer visible on the jobs through the web UI, and accessing job workspaces present a 403 error.

          "Problem accessing /job/<jobname>/ws/. Reason:

          Trying to access a file outside of the directory, target:"

          Attempted upgrade of container to OpenJDK 11, same errors occur.

          Job artifacts are created and present on local file system.  Workspace is created and present on local file system.

          Downgrading back to LTS 2.138 and the job artifacts and workspaces are visible/accessible with same IIS configuration.
          New: Using IIS reverse proxy, on LTS 2.138 artifacts and workspace were accessible through web UI as expected.  Windows Server 2016 using MSFT docker container, OpenJDK8 or 11 (currently 8) to load jenkins.war file on container start.

          After upgrade to LTS 2.150.2, or mainstream 2.164, artifacts are no longer visible on the jobs through the web UI, and accessing job workspaces present a 403 error.
          h2. HTTP ERROR 403

          Problem accessing /job/<job_name_redacted>/ws/. Reason:

          Trying to access a file outside of the directory, target:

           
          ----
          [Powered by Jetty:// 9.4.z-SNAPSHOT|http://eclipse.org/jetty]

           

          Attempted upgrade of container to OpenJDK 11, same errors occur.

          Job artifacts are created and present on local file system.  Workspace is created and present on local file system.

          Downgrading back to LTS 2.138 and the job artifacts and workspaces are visible/accessible with same IIS configuration.
          Jeremy Kam made changes -
          Description Original: Using IIS reverse proxy, on LTS 2.138 artifacts and workspace were accessible through web UI as expected.  Windows Server 2016 using MSFT docker container, OpenJDK8 or 11 (currently 8) to load jenkins.war file on container start.

          After upgrade to LTS 2.150.2, or mainstream 2.164, artifacts are no longer visible on the jobs through the web UI, and accessing job workspaces present a 403 error.
          h2. HTTP ERROR 403

          Problem accessing /job/<job_name_redacted>/ws/. Reason:

          Trying to access a file outside of the directory, target:

           
          ----
          [Powered by Jetty:// 9.4.z-SNAPSHOT|http://eclipse.org/jetty]

           

          Attempted upgrade of container to OpenJDK 11, same errors occur.

          Job artifacts are created and present on local file system.  Workspace is created and present on local file system.

          Downgrading back to LTS 2.138 and the job artifacts and workspaces are visible/accessible with same IIS configuration.
          New: Using IIS reverse proxy, on LTS 2.138 artifacts and workspace were accessible through web UI as expected.  Windows Server 2016 using MSFT docker container, OpenJDK8 or 11 (currently 8) to load jenkins.war file on container start.

          After upgrade to LTS 2.150.2, or mainstream 2.164, artifacts are no longer visible on the jobs through the web UI, and accessing job workspaces present a 403 error.
          h2. HTTP ERROR 403

          Problem accessing /job/<job_name_redacted>/ws/. Reason:

          Trying to access a file outside of the directory, target:

           
          ----
          [Powered by Jetty:// 9.4.z-SNAPSHOT|http://eclipse.org/jetty]

           

          Attempted upgrade of container to OpenJDK 11, same errors occur.

          Job artifacts are created and present on local file system.  Workspace is created and present on local file system.

          Downgrading back to LTS 2.138 and the job artifacts and workspaces are visible/accessible with same IIS configuration.

          IIS reverse proxy reference:  [https://wiki.jenkins.io/display/JENKINS/Running+Jenkins+behind+IIS] (instead of localhost and host file, used container IP address directly).  Tested as working in 2.138, fails on 2.150.2+, works correctly when reverted to 2.138.
          Jeremy Kam made changes -
          Summary Original: Artifacts and workspace not accessible after upgrade from 2.138 to 2.150.2+ (IIS reverse proxy) New: Artifacts and workspace not accessible after upgrade from LTS 2.138 to 2.150.2+ (IIS reverse proxy)
          Jeremy Kam made changes -
          Description Original: Using IIS reverse proxy, on LTS 2.138 artifacts and workspace were accessible through web UI as expected.  Windows Server 2016 using MSFT docker container, OpenJDK8 or 11 (currently 8) to load jenkins.war file on container start.

          After upgrade to LTS 2.150.2, or mainstream 2.164, artifacts are no longer visible on the jobs through the web UI, and accessing job workspaces present a 403 error.
          h2. HTTP ERROR 403

          Problem accessing /job/<job_name_redacted>/ws/. Reason:

          Trying to access a file outside of the directory, target:

           
          ----
          [Powered by Jetty:// 9.4.z-SNAPSHOT|http://eclipse.org/jetty]

           

          Attempted upgrade of container to OpenJDK 11, same errors occur.

          Job artifacts are created and present on local file system.  Workspace is created and present on local file system.

          Downgrading back to LTS 2.138 and the job artifacts and workspaces are visible/accessible with same IIS configuration.

          IIS reverse proxy reference:  [https://wiki.jenkins.io/display/JENKINS/Running+Jenkins+behind+IIS] (instead of localhost and host file, used container IP address directly).  Tested as working in 2.138, fails on 2.150.2+, works correctly when reverted to 2.138.
          New: Using IIS reverse proxy, on LTS 2.138 artifacts and workspace were accessible through web UI as expected.  Windows Server 2016 using MSFT docker container, OpenJDK8 or 11 (currently 8) to load jenkins.war file on container start.

          After upgrade to LTS 2.150.2, or mainstream 2.164, artifacts are no longer visible on the jobs through the web UI, and accessing job workspaces present a 403 error.
          h2. HTTP ERROR 403

          Problem accessing /job/<job_name_redacted>/ws/. Reason:

          Trying to access a file outside of the directory, target:

           
          ----
          [Powered by Jetty:// 9.4.z-SNAPSHOT|http://eclipse.org/jetty]

           

          Attempted upgrade of container to OpenJDK 11, same errors occur.

          Job artifacts are created and present on local file system.  Workspace is created and present on local file system.  Job will build project, just won't present the results/workspace through the UI.

          Downgrading back to LTS 2.138 and the job artifacts and workspaces are visible/accessible with same IIS configuration.

          IIS reverse proxy reference:  [https://wiki.jenkins.io/display/JENKINS/Running+Jenkins+behind+IIS] (instead of localhost and host file, used container IP address directly).  Tested as working in 2.138, fails on 2.150.2+, works correctly when reverted to 2.138.

          Daniel Beck added a comment -

          wfollonier Looks like a possible regression from your fix.

          jkam Please provide the full paths including involved reparse points (symlinks, junctions, etc.) to all directories involved here.

          Daniel Beck added a comment - wfollonier Looks like a possible regression from your fix. jkam Please provide the full paths including involved reparse points (symlinks, junctions, etc.) to all directories involved here.

          Jeremy Kam added a comment - - edited

          Job directory structure was created by Jenkins itself from initial deployment version of 2.73.2.  Upgrades through multiple LTS versions to 2.138 worked as expected.

          Jenkins uses a Docker bind mount into the container to map c:\jenkins to the external bind mount point on the host file system, and all Jenkins files reside within in the Jenkins created directory tree.

           When starting the container, docker variables and mount point:

          $HOST_JENKINS_HOME = "d:/data/jenkins"
          $JENKINS_HOME = "c:/jenkins"

          --mount type=bind,source=${HOST_JENKINS_HOME},target=${JENKINS_HOME}

          Jenkins directory listing (from within the container) included in attachment: jenkins_dir_tree_20190213_1.txt

           

          Jeremy Kam added a comment - - edited Job directory structure was created by Jenkins itself from initial deployment version of 2.73.2.  Upgrades through multiple LTS versions to 2.138 worked as expected. Jenkins uses a Docker bind mount into the container to map c:\jenkins to the external bind mount point on the host file system, and all Jenkins files reside within in the Jenkins created directory tree.  When starting the container, docker variables and mount point: $HOST_JENKINS_HOME = "d:/data/jenkins" $JENKINS_HOME = "c:/jenkins" --mount type=bind,source=${HOST_JENKINS_HOME},target=${JENKINS_HOME} Jenkins directory listing (from within the container) included in attachment: jenkins_dir_tree_20190213_1.txt  

            wfollonier Wadeck Follonier
            jkam Jeremy Kam
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: