[Bug]: Base Path regression in 2.15 #3559
Description
What happened?
When updating the docker image from 2.14 to 2.15, the frontend fails to load api/v3/services, which for us is behind a proxy ingress with a base_path. I'll attach a minimal docker compose to show the gist. With 2.14 it works fine
Steps to reproduce
docker-compose.yml
jaeger-config.yaml
nginx-jaeger.conf.txt
Note: you have to rename the nginx-jaeger.conf.txt to nginx-jaeger.conf, I wasn't allowed to upload conf files. Put the 3 files in a folder and do a docker-compose up -d, and open http://localhost:16686/api/observe/jaeger/search - everything works.
Open the docker compose file and switch 2.14.1 with 2.15.0/1 and run docker compose up -d --force-recreate jaeger nginx. Hard refresh the page - you will see the failure in the service dropdown list
Expected behavior
It works as in 2.14
Relevant log output
index-C0ABs_dT.js:1 GET http://localhost:16686/api/v3/services 404 (Not Found)
fetchWithTimeout @ index-C0ABs_dT.js:1
fetchServices @ index-C0ABs_dT.js:1
queryFn @ index-C0ABs_dT.js:1
V @ index-C0ABs_dT.js:1
cA @ index-C0ABs_dT.js:1
document.querySelector("base")?.href
'http://localhost:16686/api/observe/jaeger/'Screenshot
Additional context
No response
Jaeger backend version
cr.jaegertracing.io/jaegertracing/jaeger:2.15.1
SDK
No response
Pipeline
No response
Stogage backend
No response
Operating system
No response
Deployment model
Bug was reproduced on both kubernetes with helm and docker compose