CI failure: Deploy FuzeInfra – Production on main

[izzywdev]

@fuze the deploy workflow Deploy FuzeInfra – Production failed on main (event: push).

Run: https://github.com/izzywdev/FuzeInfra/actions/runs/33153264578

This is a deploy-path failure (not app CI). Diagnose from the run log. If it is a credential/permission problem (e.g. a token missing a scope), that is an operator action — say so plainly rather than attempting a code fix. Prod stays GitOps (edit repo -> Argo).

failed-step log (tail)

bac.authorization.k8s.io/arc-selfheal unchanged
Validate → ArgoCD sync	Wait for ArgoCD syncs to land	2026-08-28T08:07:54.9966523Z rbac.authorization.k8s.io  ClusterRoleBinding  arc-systems  arc-selfheal                         Running  Synced         clusterrolebinding.rbac.authorization.k8s.io/arc-selfheal reconciled. clusterrolebinding.rbac.authorization.k8s.io/arc-selfheal unchanged
Validate → ArgoCD sync	Wait for ArgoCD syncs to land	2026-08-28T08:07:54.9967924Z rbac.authorization.k8s.io  Role                argocd       arc-runner-argocd-apply              Synced                  role.rbac.authorization.k8s.io/arc-runner-argocd-apply reconciled. role.rbac.authorization.k8s.io/arc-runner-argocd-apply unchanged
Validate → ArgoCD sync	Wait for ArgoCD syncs to land	2026-08-28T08:07:54.9969996Z rbac.authorization.k8s.io  Role                fuzefront    arc-runner-read-registration-secret  Synced                  role.rbac.authorization.k8s.io/arc-runner-read-registration-secret reconciled. role.rbac.authorization.k8s.io/arc-runner-read-registration-secret unchanged
Validate → ArgoCD sync	Wait for ArgoCD syncs to land	2026-08-28T08:07:54.9971575Z rbac.authorization.k8s.io  Role                arc-systems  arc-selfheal                         Synced                  role.rbac.authorization.k8s.io/arc-selfheal reconciled. role.rbac.authorization.k8s.io/arc-selfheal unchanged
Validate → ArgoCD sync	Wait for ArgoCD syncs to land	2026-08-28T08:07:54.9973080Z rbac.authorization.k8s.io  RoleBinding         fuzefront    arc-runner-read-registration-secret  Synced                  rolebinding.rbac.authorization.k8s.io/arc-runner-read-registration-secret reconciled. rolebinding.rbac.authorization.k8s.io/arc-runner-read-registration-secret unchanged
Validate → ArgoCD sync	Wait for ArgoCD syncs to land	2026-08-28T08:07:54.9974600Z rbac.authorization.k8s.io  RoleBinding         arc-systems  arc-selfheal                         Synced                  rolebinding.rbac.authorization.k8s.io/arc-selfheal reconciled. rolebinding.rbac.authorization.k8s.io/arc-selfheal unchanged
Validate → ArgoCD sync	Wait for ArgoCD syncs to land	2026-08-28T08:07:54.9976637Z rbac.authorization.k8s.io  RoleBinding         argocd       arc-runner-argocd-apply              Synced                  rolebinding.rbac.authorization.k8s.io/arc-runner-argocd-apply reconciled. rolebinding.rbac.authorization.k8s.io/arc-runner-argocd-apply unchanged
Validate → ArgoCD sync	Wait for ArgoCD syncs to land	2026-08-28T08:07:54.9978011Z batch                      CronJob             arc-systems  arc-controller-selfheal              Synced   Healthy        cronjob.batch/arc-controller-selfheal unchanged
Validate → ArgoCD sync	Wait for ArgoCD syncs to land	2026-08-28T08:07:54.9979183Z rbac.authorization.k8s.io  ClusterRole                      arc-selfheal                         Synced                  
Validate → ArgoCD sync	Wait for ArgoCD syncs to land	2026-08-28T08:07:54.9979977Z rbac.authorization.k8s.io  ClusterRoleBinding               arc-selfheal                         Synced                  
Validate → ArgoCD sync	Wait for ArgoCD syncs to land	2026-08-28T08:07:55.3403714Z arc-selfheal synced and healthy
Validate → ArgoCD sync	Wait for ArgoCD syncs to land	2026-08-28T08:07:55.3406848Z ##[error]sync did not land for: fuzeinfra-prod
Validate → ArgoCD sync	Wait for ArgoCD syncs to land	2026-08-28T08:07:55.3416398Z ##[error]Process completed with exit code 1.

[izzywdev]

⚠️ Fuze responder did not run to completion

The responder errored before finishing your request, so no changes were made and no branch was created.

• Reason: Gateway could not serve claude-opus-5 (HTTP 400): {"type":"error","error":{"type":"invalid_request_error","message":"Your credit balance is too low to access the Anthropic API. Please go to Plans & Billing to upgrade or purchase credits."},"request_id":"req_011CeUogHT9tEndYNcn52nxM"}. Received Model Group=claude-opus-5
  Available Model Group Fallbacks=['gpt-4.1', 'gemini-flash-latest']
  Error doing the fallback: litellm.ServiceUnavailableError: GeminiException - {
  "error": {
  "code": 503,
  "message": "This model is currently experiencing high demand. Spikes in demand are usually temporary. Please try again later.",
  "status": "UNAVAILABLE"
  }
  }
  No fallback model group found for original model_group=gemini-flash-latest. Fallbacks=[{'claude-opus-4-5': ['gpt-4.1', 'gemini-flash-latest']}, {'claude-opus-5': ['gpt-4.1', 'gemini-flash-latest']}, {'claude-sonnet-5': ['gpt-4.1', 'gemini-flash-latest']}, {'claude-haiku-4-5': ['gpt-4.1-mini', 'gemini-flash-lite-latest']}]. Received Model Group=gemini-flash-latest
  Available Model Group Fallbacks=None
  Error doing the fallback: litellm.ServiceUnavailableError: GeminiException - {
  "error": {
  "code": 503,
  "message": "This model is currently experiencing high demand. Spikes in demand are usually temporary. Please try again later.",
  "status": "UNAVAILABLE"
  }
  }
  No fallback model group found for original model_group=gemini-flash-latest. Fallbacks=[{'claude-opus-4-5': ['gpt-4.1', 'gemini-flash-latest']}, {'claude-opus-5': ['gpt-4.1', 'gemini-flash-latest']}, {'claude-sonnet-5': ['gpt-4.1', 'gemini-flash-latest']}, {'claude-haiku-4-5': ['gpt-4.1-mini', 'gemini-flash-lite-latest']}] LiteLLM Retried: 2 times, LiteLLM Max Retries: 2 LiteLLM Retried: 2 times, LiteLLM Max Retries: 2
• Run log: https://github.com/izzywdev/FuzeInfra/actions/runs/33154146524

This notice is automated and will not retry on its own. If the LiteLLM gateway is the problem, check the LITELLM_FUZE_KEY secret and gateway health (helm/litellm/), then re-trigger by posting a new comment mentioning @fuze.