Projects page fails to load on OSS Docker image 8.0.3 — missing static chunk SdkEvaluationStatus-B1rMywp-.js

[ck1125]

Environment

• Image: unleashorg/unleash-server:8.0.3
• Deployment: Self-hosted, ECS Fargate
• Database: Aurora PostgreSQL

Behaviour

After pulling the latest / 8.0.3 image, the /projects/default page fails to load and displays an error message about a frontend module failing to load. All other pages appear unaffected.

Browser console errors

GET https://<host>/static/SdkEvaluationStatus-B1rMywp-.js net::ERR_ABORTED 404 (Not Found)
TypeError: Failed to fetch dynamically imported module: https://<host>/static/LazyProjectExport-30GlUH0L.js

Root cause

LazyProjectExport-30GlUH0L.js loads successfully (HTTP 200) but dynamically imports SdkEvaluationStatus-B1rMywp-.js, which returns 404 from the server. The chunk is present in the main bundle's import graph but missing from the Docker image's static assets.

Workaround

Pinning to unleashorg/unleash-server:8.0.2 resolves the issue — the Projects page loads correctly on that image.

Steps to reproduce

1. Run unleashorg/unleash-server:8.0.3
2. Navigate to /projects/default
3. Observe the error page and the 404 for SdkEvaluationStatus-B1rMywp-.js in the browser network tab

Expected behaviour

The Projects page loads correctly, as it did on 8.0.2.

[gastonfournier]

Thanks for the report. We've confirmed that the referenced SdkEvaluationStatus-B1rMywp-.js file is present in the 8.0.3 image, so we're investigating whether this could happen during the rollout itself.

Could you share a few details about how you deploy new versions on ECS Fargate?

• Do the old and new tasks receive traffic simultaneously during a rolling deployment?
• Is session stickiness enabled on the load balancer?
• Did the error occur only while deploying 8.0.3, or did it continue after all 8.0.2 tasks had been terminated?
• Does a hard refresh after the rollout completes resolve the problem?
• Are the HTML responses or static assets cached by a CDN, reverse proxy, or load balancer?

Our current hypothesis is that the browser loaded the 8.0.3 HTML from one server, then requested its newly named JavaScript asset from an 8.0.2 server. These details would help us confirm that and determine whether we can make UI asset delivery safer across rolling deployments.