Skip to content

LCORE-4751: remove ogx_version from GET /v1/info - #3133

Open
max-svistunov wants to merge 1 commit into
lightspeed-core:mainfrom
max-svistunov:lcore-4751-remove-ogx-version-from-info
Open

max-svistunov wants to merge 1 commit into
lightspeed-core:mainfrom
max-svistunov:lcore-4751-remove-ogx-version-from-info

Conversation

@max-svistunov

Copy link
Copy Markdown
Contributor

Description

LCORE-4751: GET /v1/info becomes an LCORE identity endpoint. It returns name and service_version only and no longer calls OGX inspect.version(). The ogx_version field is removed from InfoResponse with no replacement, as the ticket and the catalog and health endpoints design ask.

Visible API changes, both recorded in docs/migrations/v0.8.0.md:

  • ogx_version is gone from the response.
  • With OGX unreachable, the endpoint now answers 200 instead of 503 Unable to connect to OGX. Use GET /readiness to detect whether OGX is available.

ogx_version was never marked deprecated, so this removes it without the usual deprecation phase of one minor release. The removal follows the design doc, and llama_stack_version was dropped the same way in 0.7. If a deprecation phase is preferred, the field can stay in 0.8 marked deprecated, with the removal moved to the next minor release.

The endpoint keeps 503 in its documented responses because Kubernetes authentication can still return it; only the OGX example is dropped. src/app/main.py and src/utils/ogx_version.py are unchanged: the startup version check still needs them.

OpenAPI and the model docs are updated. The e2e scenario in ogx_disrupted.feature now expects 200 instead of 503, and the unused ogx version step is removed.

Type of change

  • Refactor
  • New feature
  • Bug fix
  • CVE fix
  • Optimization
  • Documentation Update
  • Configuration Update
  • Bump-up service version
  • Bump-up dependent library [pyproject.toml + uv.lock]
  • Bump-up dependent library [requirements.*.txt for Konflux]
  • Bump-up library or tool used for development (does not change the final image)
  • CI configuration change
  • Konflux configuration change
  • Unit tests improvement
  • Integration tests improvement
  • End to end tests improvement
  • Benchmarks improvement

Tools used to create PR

Identify any AI code assistants used in this PR (for transparency and review context)

  • Assisted-by: Claude Opus 4.8
  • Generated by: Claude Opus 4.8

Related Tickets & Documents

  • Related Issue # LCORE-4751
  • Closes # LCORE-4751

Checklist before requesting a review

  • I have performed a self-review of my code.
  • PR has passed all pre-merge test jobs.
  • If it is a core feature, I have added thorough tests.

Testing

  • Please provide detailed steps to perform tests related to this code change.
  • How were the fix/results from this change verified? Please provide relevant screenshots or results.
  1. Mount the info router on a FastAPI app with noop authentication, point ogx.url at a closed port, and call GET /v1/info. Expected: 200 with only name and service_version. Actual: 200 {"name":"http-check","service_version":"0.8.0rc1"}.
  2. Run the tests for the change: .venv/bin/python -m pytest tests/unit/app/endpoints/test_info.py tests/unit/models/responses/test_successful_responses.py::TestInfoResponse tests/unit/utils/dumpers/test_models_dumper.py tests/integration/endpoints/test_info_integration.py. They all pass.
  3. Run the full suites. Unit: 4039 passed, 1 skipped. Integration, without tests/integration/container_lifecycle: 372 passed.
  4. Run the e2e scenarios: tests/e2e/features/info.feature and tests/e2e/features/ogx_disrupted.feature. These were not run against a live stack for this PR; a behave --dry-run confirms that all their steps resolve, so the CI e2e jobs are their first real run.

Keep /v1/info as an LCORE identity endpoint that returns name and
service_version only. Drop the OGX inspect.version() call, the
ogx_version field of InfoResponse and the now unreachable OGX error
handling, so the endpoint answers 200 while OGX is unreachable instead
of 503. The 503 stays documented for the Kubernetes authentication
backend. The startup version check in src/utils/ogx_version.py is
unchanged.

Update unit, integration and e2e tests, including the ogx_disrupted
scenario, regenerate the OpenAPI and model docs, and add the change to
the v0.8.0 migration notes.
@coderabbitai

coderabbitai Bot commented Nov 3, 2026

Copy link
Copy Markdown
Contributor

Warning

Review limit reached

You've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository.

Next included review available in 31 minutes.

Check out review usage here.

View limit details

Limit details: You’ve used the included review currently available.

Learn how review limits work.

Review configuration:

Run configuration
Commits

Reviewing files that changed from the base of the PR and between 1aee84a and fd41f4b.

Files ignored due to path filters: 1
  • docs/models/responses.svg is excluded by !**/*.svg
Files selected for processing: 18
  • docs/devel_doc/openapi.json
  • docs/devel_doc/openapi.md
  • docs/migrations/index.md
  • docs/migrations/v0.8.0.md
  • docs/models/responses.puml
  • docs/models/successful_responses.json
  • docs/models/successful_responses.md
  • docs/testing/e2e_scenarios.md
  • docs/testing/integration_vs_e2e.md
  • src/app/endpoints/info.py
  • src/models/api/responses/successful/probes.py
  • tests/e2e/features/info.feature
  • tests/e2e/features/ogx_disrupted.feature
  • tests/e2e/features/steps/info.py
  • tests/integration/endpoints/test_info_integration.py
  • tests/unit/app/endpoints/test_info.py
  • tests/unit/models/responses/test_successful_responses.py
  • tests/unit/utils/dumpers/test_models_dumper.py
  • Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

Share

CodeRabbit Verify

  • Run CodeRabbit Verify to test the changes in this pull request.

@tisnik tisnik left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants