dosubot[bot] commented on issue #36602: URL: https://github.com/apache/superset/issues/36602#issuecomment-3654136260
<!-- Answer --> Thanks for clarifying your setup. With the official Helm chart, Python 3.10+, and a root-path deployment, you’ve ruled out the most common causes like asset build issues and subpath/proxy misconfigurations. There aren’t any known bugs or recent changes in Superset 6.0.0rc4 that would cause intermittent 404/405 errors specifically for root-path deployments—the new AppRootMiddleware only affects subpath setups, and isn’t active when running at `/` [citation](https://github.com/apache/superset/blob/829e4d92d91ceae4b43b1ed3b063ffe45377799c/superset/app.py#L41-L107). Ingress controllers and health probes are a frequent source of unexpected 404s/405s, especially after upgrades. When you review your ingress and backend logs, look for patterns like liveness/readiness probes, rewritten paths, or annotations that might be sending requests to endpoints that don’t exist in Superset. If you spot any consistent failing paths or actions, share them here—I’m happy to help dig into any subtle routing or middleware edge cases if needed. <!-- Dosu Comment Footer --> *To reply, just mention [@dosu](https://go.dosu.dev/dosubot).* --- <sup>How did I do? [Good](https://app.dosu.dev/response-feedback/9e308e40-e3da-4d91-aa13-6c2ada819369?feedback_type=great_response) | [Irrelevant](https://app.dosu.dev/response-feedback/9e308e40-e3da-4d91-aa13-6c2ada819369?feedback_type=irrelevant_answer) | [Incorrect](https://app.dosu.dev/response-feedback/9e308e40-e3da-4d91-aa13-6c2ada819369?feedback_type=incorrect_sources) | [Verbose](https://app.dosu.dev/response-feedback/9e308e40-e3da-4d91-aa13-6c2ada819369?feedback_type=too_verbose) | [Hallucination](https://app.dosu.dev/response-feedback/9e308e40-e3da-4d91-aa13-6c2ada819369?feedback_type=hallucination) | [Report 🐛](https://app.dosu.dev/response-feedback/9e308e40-e3da-4d91-aa13-6c2ada819369?feedback_type=bug_report) | [Other](https://app.dosu.dev/response-feedback/9e308e40-e3da-4d91-aa13-6c2ada819369?feedback_type=other)</sup> [](https://app.dosu.dev/a28d3c7e-a9d3-459e-9fb6-3a6f9ff4f357/ask?utm_source=github) [](https://cursor.com/link/prompt?text=Thanks%20for%20clarifying%20your%20setup.%20With%20the%20official%20Helm%20chart%2C%20Python%203.10%2B%2C%20and%20a%20root-path%20deployment%2C%20you%E2%80%99ve%20ruled%20out%20the%20most%20common%20causes%20like%20asset%20build%20issues%20and%20subpath/proxy%20misconfigurations.%20There%20aren%E2%80%99t%20any%20known%20bugs%20or%20recent%20changes%20in%20Superset%206.0.0rc4%20that%20would%20cause%20intermittent%20404/405%20errors%20specifically%20for%20root-path%20deployments%E2%80%94the%20new%20AppRootMiddleware%20only%20affects%20subpath%20setups%2C%20and%20isn%E2%80%99t%20active%20when%20running%20at%20%60/%60%C2%A0%5Bcitation%5D%28https%3A//github.com/apache/superset/blob/829e4d92d91ceae4b43b1ed3b063ffe45377799c/superset/app.py%23L41-L107%29.% 0A%0AIngress%20controllers%20and%20health%20probes%20are%20a%20frequent%20source%20of%20unexpected%20404s/405s%2C%20especially%20after%20upgrades.%20When%20you%20review%20your%20ingress%20and%20backend%20logs%2C%20look%20for%20patterns%20like%20liveness/readiness%20probes%2C%20rewritten%20paths%2C%20or%20annotations%20that%20might%20be%20sending%20requests%20to%20endpoints%20that%20don%E2%80%99t%20exist%20in%20Superset.%20If%20you%20spot%20any%20consistent%20failing%20paths%20or%20actions%2C%20share%20them%20here%E2%80%94I%E2%80%99m%20happy%20to%20help%20dig%20into%20any%20subtle%20routing%20or%20middleware%20edge%20cases%20if%20needed.) [](https://go.dosu.dev/discord-bot) [](https://twitter.com/intent/tweet?text=%40dosu_ai%20helped%20me%20solve%20this%20issue!&url=https%3A//github.com/apache/superset/issues/36602) -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
