Merge pull request #67 from rh-aiservices-bu/dev

chore: release v0.1.2 - fix critical migration issue

Author: guimou

CHANGELOG.md

@@ -5,6 +5,26 @@ All notable changes to this project are documented in this file.
 The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.0.0/),
 and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
 
+## [0.1.2] - 2025-10-17
+
+This patch release fixes a critical database migration issue that could prevent successful deployments.
+
+### Fixed
+
+- **Database Migration Resilience**: Fixed `litellm_key_alias` backfill migration to skip inactive API keys
+  - Migration now filters for `is_active = true` to avoid processing inactive/revoked keys
+  - Prevents 404 errors from LiteLLM when trying to fetch details for deleted keys
+  - Eliminates circuit breaker opening after 5 consecutive failures
+  - Ensures active keys are successfully processed during backfill operations
+  - Added explanatory comment about skipping inactive keys
+
+### Contributors
+
+- Guillaume Moutier
+- Co-authored-by: Claude (AI pair programming assistant)
+
+---
+
 ## [0.1.1] - 2025-10-17
 
 This patch release improves test reliability, server startup performance, and handles edge cases in database migrations.

backend/src/lib/database-migrations.ts

@@ -637,14 +637,16 @@ COMMENT ON COLUMN subscriptions.status_changed_by IS 'Existing subscriptions mig
 export const backfillLiteLLMKeyAlias = async (dbUtils: DatabaseUtils, liteLLMService: any) => {
   try {
     // Find all API keys that don't have litellm_key_alias set
+    // Only process active keys to avoid 404s from inactive/revoked keys
     const keysToBackfill = await dbUtils.queryMany<{
       id: string;
       lite_llm_key_value: string;
     }>(
       `SELECT id, lite_llm_key_value
        FROM api_keys
        WHERE litellm_key_alias IS NULL
-         AND lite_llm_key_value IS NOT NULL`,
+         AND lite_llm_key_value IS NOT NULL
+         AND is_active = true`,
       [],
     );
 

deployment/openshift/README.md

@@ -32,7 +32,7 @@ The deployment uses a **template-based configuration system**:
    ```
 
 2. **Edit `user-values.env`** and customize the following **required values**:
-   - `LITEMAAS_VERSION` - LiteMaaS version to deploy (e.g., `0.1.0`)
+   - `LITEMAAS_VERSION` - LiteMaaS version to deploy (e.g., `0.1.2`)
    - `CLUSTER_DOMAIN_NAME` - Your OpenShift cluster domain (e.g., `apps.cluster.example.com`)
    - `NAMESPACE` - Namespace/project name (e.g., `litemaas`)
    - `PG_ADMIN_PASSWORD` - Secure PostgreSQL password (generate with `openssl rand -base64 32`)

deployment/openshift/user-values.env.example

@@ -1,4 +1,4 @@
-LITEMAAS_VERSION=0.1.0
+LITEMAAS_VERSION=0.1.2
 CLUSTER_DOMAIN_NAME=your-cluster-domain
 NAMESPACE=your-namespace
 PG_ADMIN_PASSWORD=change-me-pg-password

package.json

@@ -1,6 +1,6 @@
 {
   "name": "litemaas",
-  "version": "0.1.1",
+  "version": "0.1.2",
   "description": "LiteLLM User Application - Model subscription and management platform",
   "private": true,
   "workspaces": [