Skip to content

OLS-3060: Add GET /ready readiness endpoint#48

Open
onmete wants to merge 2 commits into
openshift:mainfrom
onmete:ols-3060-ready-endpoint
Open

OLS-3060: Add GET /ready readiness endpoint#48
onmete wants to merge 2 commits into
openshift:mainfrom
onmete:ols-3060-ready-endpoint

Conversation

@onmete
Copy link
Copy Markdown
Contributor

@onmete onmete commented May 20, 2026

Summary

  • Add GET /ready readiness probe per health-probes.md (OLS-3058 spike)
  • R1 provider_env: credential env var present for LIGHTSPEED_AGENT_PROVIDER (claude / gemini / openai)
  • R2 provider_endpoint: unauthenticated HTTP GET (3s timeout); any HTTP response including 4xx counts as reachable
  • Returns 200 {"status":"ok"} or 503 with per-check checks map
  • GET /health unchanged in app.py — independent of OLS-3059 / OLS-3059: Extract GET /health liveness endpoint #47

Related

Test plan

  • make test (30 tests; R2 mocked — no live network)
  • make lint

Made with Cursor

Independent of liveness refactor (OLS-3059). GET /health stays in app.py;
readiness lives in health.py with provider_env and provider_endpoint checks
per health-probes.md.

Co-authored-by: Cursor <cursoragent@cursor.com>
@openshift-ci-robot
Copy link
Copy Markdown

openshift-ci-robot commented May 20, 2026

@onmete: An error was encountered searching for bug OLS-3060 on the Jira server at https://redhat.atlassian.net. No known errors were detected, please see the full error message for details.

Full error message. No response returned: Get "https://redhat.atlassian.net/rest/api/2/issue/OLS-3060": GET https://redhat.atlassian.net/rest/api/2/issue/OLS-3060 giving up after 5 attempt(s)

Please contact an administrator to resolve this issue, then request a bug refresh with /jira refresh.

Details

In response to this:

Summary

  • Add GET /ready readiness probe per health-probes.md (OLS-3058 spike)
  • R1 provider_env: credential env var present for LIGHTSPEED_AGENT_PROVIDER (claude / gemini / openai)
  • R2 provider_endpoint: unauthenticated HTTP GET (3s timeout); any HTTP response including 4xx counts as reachable
  • Returns 200 {"status":"ok"} or 503 with per-check checks map
  • GET /health unchanged in app.py — independent of OLS-3059 / OLS-3059: Extract GET /health liveness endpoint #47

Related

Test plan

  • make test (30 tests; R2 mocked — no live network)
  • make lint

Made with Cursor

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

@openshift-ci-robot openshift-ci-robot added the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label May 20, 2026
@openshift-ci-robot
Copy link
Copy Markdown

@onmete: This pull request references OLS-3060 which is a valid jira issue.

Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the story to target the "5.0.0" version, but no target version was set.

Details

In response to this:

Summary

  • Add GET /ready readiness probe per health-probes.md (OLS-3058 spike)
  • R1 provider_env: credential env var present for LIGHTSPEED_AGENT_PROVIDER (claude / gemini / openai)
  • R2 provider_endpoint: unauthenticated HTTP GET (3s timeout); any HTTP response including 4xx counts as reachable
  • Returns 200 {"status":"ok"} or 503 with per-check checks map
  • GET /health unchanged in app.py — independent of OLS-3059 / OLS-3059: Extract GET /health liveness endpoint #47

Related

Test plan

  • make test (30 tests; R2 mocked — no live network)
  • make lint

Made with Cursor

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

@openshift-ci openshift-ci Bot requested review from harche and joshuawilson May 20, 2026 12:41
@openshift-ci
Copy link
Copy Markdown

openshift-ci Bot commented May 20, 2026

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:
Once this PR has been reviewed and has the lgtm label, please assign xrajesh for approval. For more information see the Code Review Process.

The full list of commands accepted by this bot can be found here.

Details Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

Readiness must not assume claude when the operator omits provider
config; returns 503 until the env var is set explicitly.

Co-authored-by: Cursor <cursoragent@cursor.com>
@openshift-ci
Copy link
Copy Markdown

openshift-ci Bot commented May 21, 2026

@onmete: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name Commit Details Required Rerun command
ci/prow/e2e-openai 1667ebc link true /test e2e-openai

Full PR test history. Your PR dashboard.

Details

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here.

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

Labels

jira/valid-reference Indicates that this PR references a valid Jira ticket of any type.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants