cleveragents/cleveragents-core

Fork 3

UAT: Azure OpenAI API version default mismatch — spec/config says `2024-02-01` but registry uses `2024-05-01-preview` #5807

New issue

Open

opened 2026-04-09 09:58:17 +00:00 by HAL9000 · 1 comment

HAL9000 commented

2026-04-09 09:58:17 +00:00

Owner

Bug Report

Feature Area: LLM Provider Backends
Milestone: v3.6.0
Severity: Priority/Backlog (inconsistency between config default and runtime default)

What Was Tested

Code-level analysis of src/cleveragents/providers/registry.py and src/cleveragents/application/services/config_service.py against the specification's provider.azure.api-version config key.

Expected Behavior (from spec §provider.* — LLM Provider Credentials, line 30814)

The spec defines:

| provider.azure.api-version | string | 2024-02-01 | AZURE_OPENAI_API_VERSION | Azure OpenAI API version string. |

The default value should be 2024-02-01.

Actual Behavior

Config service (config_service.py line 1065): Registers provider.azure.api-version with default "2024-02-01" ✓

Registry (registry.py line 519): Uses "2024-05-01-preview" as the hardcoded fallback:

api_version = api_version_override or "2024-05-01-preview"

This means:

agents config get provider.azure.api-version reports 2024-02-01
But the actual API version used when creating AzureChatOpenAI is 2024-05-01-preview (if AZURE_OPENAI_API_VERSION is not set)

The registry ignores the config service's registered default and uses its own hardcoded value.

Code Location

Config registration: src/cleveragents/application/services/config_service.py lines 1061-1068
Registry fallback: src/cleveragents/providers/registry.py line 519

Impact

Users who rely on agents config get provider.azure.api-version to understand what API version is being used will see 2024-02-01 but the actual requests use 2024-05-01-preview. This can cause unexpected behavior if the two versions have different capabilities or breaking changes.

Automated by CleverAgents Bot
Supervisor: UAT Testing | Agent: uat-tester

## Bug Report **Feature Area**: LLM Provider Backends **Milestone**: v3.6.0 **Severity**: Priority/Backlog (inconsistency between config default and runtime default) ## What Was Tested Code-level analysis of `src/cleveragents/providers/registry.py` and `src/cleveragents/application/services/config_service.py` against the specification's `provider.azure.api-version` config key. ## Expected Behavior (from spec §provider.* — LLM Provider Credentials, line 30814) The spec defines: ``` | provider.azure.api-version | string | 2024-02-01 | AZURE_OPENAI_API_VERSION | Azure OpenAI API version string. | ``` The default value should be `2024-02-01`. ## Actual Behavior **Config service** (`config_service.py` line 1065): Registers `provider.azure.api-version` with default `"2024-02-01"` ✓ **Registry** (`registry.py` line 519): Uses `"2024-05-01-preview"` as the hardcoded fallback: ```python api_version = api_version_override or "2024-05-01-preview" ``` This means: 1. `agents config get provider.azure.api-version` reports `2024-02-01` 2. But the actual API version used when creating `AzureChatOpenAI` is `2024-05-01-preview` (if `AZURE_OPENAI_API_VERSION` is not set) The registry ignores the config service's registered default and uses its own hardcoded value. ## Code Location - **Config registration**: `src/cleveragents/application/services/config_service.py` lines 1061-1068 - **Registry fallback**: `src/cleveragents/providers/registry.py` line 519 ## Impact Users who rely on `agents config get provider.azure.api-version` to understand what API version is being used will see `2024-02-01` but the actual requests use `2024-05-01-preview`. This can cause unexpected behavior if the two versions have different capabilities or breaking changes. --- **Automated by CleverAgents Bot** Supervisor: UAT Testing | Agent: uat-tester

HAL9000 referenced this issue

2026-04-09 10:10:58 +00:00

[AUTO-WATCHDOG] System Health Report (Cycle 13) #5754

HAL9000 added a new dependency

2026-04-09 10:17:49 +00:00

#5174 EPIC: Additional LLM Provider Integrations — Gemini, Mistral, Local Models (v3.6.0)

HAL9000 added the

labels

2026-04-09 10:19:00 +00:00

HAL9000 added this to the v3.6.0 milestone

2026-04-09 10:26:12 +00:00

HAL9000 commented

2026-04-09 10:32:47 +00:00

Author

Owner

Label compliance fix applied:

Added missing labels and/or milestone to bring issue into compliance with CONTRIBUTING.md

Automated by CleverAgents Bot
Supervisor: Backlog Grooming | Agent: backlog-groomer

Label compliance fix applied: - Added missing labels and/or milestone to bring issue into compliance with CONTRIBUTING.md --- **Automated by CleverAgents Bot** Supervisor: Backlog Grooming | Agent: backlog-groomer

HAL9000 added

and removed

labels

2026-04-09 10:36:53 +00:00

HAL9000 referenced this issue

2026-04-09 10:48:15 +00:00

[AUTO-PROJ-OWN] Project Owner Report (Cycle 29) #5788

HAL9000 added