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

Configure screen: Resource Root URL validation error - 404 instance-identity

    Details

    • Similar Issues:
    • Released As:
      Jenkins 2.235

      Description

      It seems that something is wrong in how this validation is performed.

      This is reproduceable running locally with:

        Attachments

          Issue Links

            Activity

            Hide
            build_admiral Fred Vogt added a comment - - edited

            Jenkins 2.234, AWS ec2 instance running jenkins container.

            Jenkins URL: https://jenkins-backend.dev.cicdenv.com/
            Resoure Root URL: https://builds-backend.dev.cicdenv.com/

            Both DNS names go to an AWS ALB with host routing rules.

            jenkins:
            crumbIssuer:
            standard:
            excludeClientIPFromCrumb: true

            The server/resource root URLs are set in groovy hooky scripts:
            JenkinsLocationConfiguration.get().url = ...
            ResourceDomainConfiguration.get().url = ...

            I haven't used a separate resource root url before.
            https://github.com/jenkinsci/jenkins/pull/4239

            I put a custom logo override into userContent and it is working which leads me to believe the resource root url setting is working, however the check against /instance-identity/ is failing in the configure page.

            I don't think this problem is new in version 2.234.

            Show
            build_admiral Fred Vogt added a comment - - edited Jenkins 2.234, AWS ec2 instance running jenkins container. Jenkins URL: https://jenkins-backend.dev.cicdenv.com/ Resoure Root URL: https://builds-backend.dev.cicdenv.com/ Both DNS names go to an AWS ALB with host routing rules. jenkins: crumbIssuer: standard: excludeClientIPFromCrumb: true The server/resource root URLs are set in groovy hooky scripts: JenkinsLocationConfiguration.get().url = ... ResourceDomainConfiguration.get().url = ... I haven't used a separate resource root url before. https://github.com/jenkinsci/jenkins/pull/4239 I put a custom logo override into userContent and it is working which leads me to believe the resource root url setting is working, however the check against /instance-identity/ is failing in the configure page. I don't think this problem is new in version 2.234.
            Hide
            danielbeck Daniel Beck added a comment -

            I am able to reproduce it with a 2.234 docker image. Weird, I specifically tested this.

            Show
            danielbeck Daniel Beck added a comment - I am able to reproduce it with a 2.234 docker image. Weird, I specifically tested this.
            Hide
            danielbeck Daniel Beck added a comment -

            This worked as intended in 2.200.

            Show
            danielbeck Daniel Beck added a comment - This worked as intended in 2.200.
            Hide
            danielbeck Daniel Beck added a comment -

            This broke in 2.205 because of the Winstone update that changed the 404 error message format.

            The form validation expects a message to occur in a 404 error response and it seems it no longer matches exactly. That's the only difference between the "404 Not Found" error, and "This is a previously set up resource domain".

            Show
            danielbeck Daniel Beck added a comment - This broke in 2.205 because of the Winstone update that changed the 404 error message format. The form validation expects a message to occur in a 404 error response and it seems it no longer matches exactly. That's the only difference between the "404 Not Found" error, and "This is a previously set up resource domain".
            Hide
            danielbeck Daniel Beck added a comment -

            Upstream regression is https://github.com/eclipse/jetty.project/issues/4154 (and rejected).

            Show
            danielbeck Daniel Beck added a comment - Upstream regression is https://github.com/eclipse/jetty.project/issues/4154 (and rejected).
            Hide
            danielbeck Daniel Beck added a comment -

            Just to confirm,

            I put a custom logo override into userContent and it is working which leads me to believe the resource root url setting is working, however the check against /instance-identity/ is failing in the configure page.

            This is correct; it's just the form validation that's affected, as it can no longer distinguish a 404 response from a resource root URL from just any other 404 response.

            Show
            danielbeck Daniel Beck added a comment - Just to confirm, I put a custom logo override into userContent and it is working which leads me to believe the resource root url setting is working, however the check against /instance-identity/ is failing in the configure page. This is correct; it's just the form validation that's affected, as it can no longer distinguish a 404 response from a resource root URL from just any other 404 response.
            Hide
            build_admiral Fred Vogt added a comment -

            Daniel Beck - thanks for responding and diagnosing so quickly.

            Show
            build_admiral Fred Vogt added a comment - Daniel Beck - thanks for responding and diagnosing so quickly.

              People

              • Assignee:
                danielbeck Daniel Beck
                Reporter:
                build_admiral Fred Vogt
              • Votes:
                0 Vote for this issue
                Watchers:
                2 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: