[Incident][108dev] Avatar speech token broker unavailable (missing speech/AI runtime config)

Open
#147 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
38/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Stale
Tech stack
azure, python
Domain
ci-cd, cloud, infrastructure

Research direction

Start with the tutor-avatar-108dev runtime configuration and deployment checks, then verify the named /api/avatar/health, /ready, /speech/session-token, and /response entry points. Done means the four required variables are populated, speech and response flows succeed, and deployment guardrails plus post-deploy smoke checks cover missing configuration.

Written by the indexing model from the issue text.

Description

Summary

Avatar speech and response flows are degraded in 108dev due to missing runtime configuration.

Evidence

  • GET /api/avatar/speech/session-token returns 503
  • Response detail:
    • Speech token broker unavailable: Speech broker is not configured. Set SPEECH_RESOURCE_ID and SPEECH_REGION.
  • Runtime env on tutor-avatar-108dev shows empty:
    • SPEECH_RESOURCE_ID
    • SPEECH_REGION
    • PROJECT_ENDPOINT
    • MODEL_DEPLOYMENT_NAME
  • GET /api/avatar/health and /ready return 200 (service up but partially broken)
  • Container Apps specialist found candidate AI/Speech resource in RG:
    • /subscriptions/150e82e8-25db-4f1a-8e04-a2f6a77d26c4/resourceGroups/tutor-108dev/providers/Microsoft.CognitiveServices/accounts/tutor108dev4p86ctai
    • region westus3

Impact

  • Speech token brokering fails for Avatar UI.
  • Avatar conversational path is at risk due empty AI endpoint/deployment config.

Proposed remediation

  1. Set SPEECH_RESOURCE_ID + SPEECH_REGION on avatar app.
  2. Set PROJECT_ENDPOINT + MODEL_DEPLOYMENT_NAME on avatar app.
  3. Add deploy guardrail checks for these required vars.
  4. Add post-deploy avatar smoke checks (/speech/session-token, /response).
Dominant language
Python
Stars
17
Forks
8
No merged PRs in 30d

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from Azure-Samples/tutor

All issues in Azure-Samples/tutor

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.