Instance console fails with service_http_failure instead of opening the console #16
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
User reports Console fails with: "The cloud service returned an HTTP error. Use Check APIs for its status code. (service_http_failure)". Inspect Nova console request routing/microversion/type, SDK wire behavior, response status handling and Horizon console fallback behavior. Reproduce supported and rejected console responses using synthetic local resources; do not expose console URLs/tokens in diagnostics or mutate real cloud resources.
Implemented and pushed in
59d3fa2.The user confirmed that Horizon works with SPICE. The previous fixed noVNC default has been replaced by Automatic console selection (noVNC, SPICE HTML5, WebMKS), with explicit selection retained. Only HTTP 400/501 permit type fallback; policy/authentication/rate/transport/other server failures stop. Successful type preference is kept per transport session; URLs/tokens are never cached. Failed console requests now show HTTP status in the dialog.
Validated using the actual SDK against a disposable HTTPS SPICE-only provider, including request protocol/body, Nova microversion, remembered type, explicit type, failure boundaries and unsafe URLs. Browser integration confirmed automatic selection, returned SPICE type, explicit external opener and HTTP error display. Svelte check and production frontend build passed.
The desktop app including its Python worker and native wire-key allowlist must be rebuilt. A live SPICE session in the user's cloud has not been verified here; native/live acceptance remains tracked by #10.