-
Bug
-
Resolution: Fixed
-
Minor
-
Jenkins 2.234 local or AWS
-
-
Jenkins 2.235
It seems that something is wrong in how this validation is performed.
This is reproduceable running locally with:
- server url: https://localhost:8443
- resource root url: https://127.0.0.1:8443
- links to
[JENKINS-62133] Configure screen: Resource Root URL validation error - 404 instance-identity
Environment |
Original:
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 JenkinsLocationConfiguration.get().url = ... ResourceDomainConfiguration.get().url = ... |
New: Jenkins 2.234 local or AWS |
Summary | Original: Resource Root URL shows 404 validation error in configure screen | New: Configure screen Resource Root URL validation error - 404 instance-identity |
Attachment | Original: Screen Shot 2020-04-30 at 15.06.40.png [ 51130 ] |
Attachment | Original: Screen Shot 2020-04-30 at 15.09.29.png [ 51128 ] |
Attachment | Original: Screen Shot 2020-04-30 at 15.08.29.png [ 51129 ] |
Attachment | New: sample-server-url-2020-04-30.png [ 51131 ] |
Attachment | New: sample-resource-root-url-2020-04-30.png [ 51132 ] |
Attachment | New: sample-resource-root-url-reachale-2020-04-30.png [ 51133 ] |
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.