After deployment on the prod-3 cluster, NextGenUI got stuck on the initial loading screen. The issue was observed immediately during post-deployment sanity.
We identified the problem to be with our required static resources failing to load. This release included a change to how we build and load the UI for different environments. The change involved making the source for static-files configurable per-environment. But an incompatible configuration for the prod-3 cluster prevented the correct URL from being formed, resulting in 404 for our JS resources.
We mitigated the incident by updating the service configuration for this environment and re-deploying the Nextgen UI service. With the new configuration, the UI service was able to generate the correct URLs, and the issue was resolved.
Time (UTC) | Event |
---|---|
12:44 AM | Incident was first detected after the new deployment. An internal incident was raised, and the team started looking into the issue. |
12:46 AM | Root cause identified and the fix was deployed. |
12:47 AM | Incident resolved |