Skip to content

fix: wait for llama-stack health condition#481

Merged
dbasunag merged 1 commit intoopendatahub-io:mainfrom
jgarciao:fix-rag-timing-bug-lls-ready
Aug 1, 2025
Merged

fix: wait for llama-stack health condition#481
dbasunag merged 1 commit intoopendatahub-io:mainfrom
jgarciao:fix-rag-timing-bug-lls-ready

Conversation

@jgarciao
Copy link
Copy Markdown
Contributor

@jgarciao jgarciao commented Aug 1, 2025

Fixes timing issue when the LlamaStackDistribition is not ready, causing the llama-stack service portforwarding to fail

Fixes timing issue when the LlamaStackDistribition is not ready, causing
the llama-stack service portforwarding to fail

Signed-off-by: Jorge Garcia Oncins <jgarciao@redhat.com>
@jgarciao jgarciao requested a review from a team as a code owner August 1, 2025 12:57
@coderabbitai
Copy link
Copy Markdown
Contributor

coderabbitai bot commented Aug 1, 2025

📝 Walkthrough

Summary by CodeRabbit

  • Tests
    • Improved reliability of tests by ensuring health checks complete before proceeding.

Walkthrough

A call to wait_for_condition was added in the llama_stack_distribution_from_template fixture within the test configuration. This ensures the "HealthCheck" condition is "True" with a timeout of 240 seconds before proceeding. No other logic or exported entities were changed.

Changes

Cohort / File(s) Change Summary
Test Fixture Update
tests/rag/conftest.py
Added a wait_for_condition call in the llama_stack_distribution_from_template fixture to ensure the "HealthCheck" is "True" before yielding.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

✨ Finishing Touches
  • 📝 Generate Docstrings
🧪 Generate unit tests
  • Create PR with unit tests
  • Post copyable unit tests in a comment

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
🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>, please review it.
    • Explain this complex logic.
    • Open a follow-up GitHub issue for this discussion.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
    • @coderabbitai explain this code block.
    • @coderabbitai modularize this function.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
    • @coderabbitai read src/utils.ts and explain its main purpose.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
    • @coderabbitai help me debug CodeRabbit configuration file.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai full review to do a full review from scratch and review all the files again.
  • @coderabbitai summary to regenerate the summary of the PR.
  • @coderabbitai generate docstrings to generate docstrings for this PR.
  • @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this PR.
  • @coderabbitai generate unit tests to generate unit tests for this PR.
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @coderabbitai help to get help.

Other keywords and placeholders

  • Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
  • Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
  • Add @coderabbitai anywhere in the PR title to generate the title automatically.

Documentation and Community

  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

@github-actions
Copy link
Copy Markdown

github-actions bot commented Aug 1, 2025

The following are automatically added/executed:

  • PR size label.
  • Run pre-commit
  • Run tox
  • Add PR author as the PR assignee
  • Build image based on the PR

Available user actions:

  • To mark a PR as WIP, add /wip in a comment. To remove it from the PR comment /wip cancel to the PR.
  • To block merging of a PR, add /hold in a comment. To un-block merging of PR comment /hold cancel.
  • To mark a PR as approved, add /lgtm in a comment. To remove, add /lgtm cancel.
    lgtm label removed on each new commit push.
  • To mark PR as verified comment /verified to the PR, to un-verify comment /verified cancel to the PR.
    verified label removed on each new commit push.
  • To Cherry-pick a merged PR /cherry-pick <target_branch_name> to the PR. If <target_branch_name> is valid,
    and the current PR is merged, a cherry-picked PR would be created and linked to the current PR.
  • To build and push image to quay, add /build-push-pr-image in a comment. This would create an image with tag
    pr-<pr_number> to quay repository. This image tag, however would be deleted on PR merge or close action.
Supported labels

{'/lgtm', '/wip', '/build-push-pr-image', '/hold', '/verified', '/cherry-pick'}

@jgarciao
Copy link
Copy Markdown
Contributor Author

jgarciao commented Aug 1, 2025

/verified

Copy link
Copy Markdown
Contributor

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

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

Actionable comments posted: 0

🧹 Nitpick comments (1)
tests/rag/conftest.py (1)

79-87: Hard-coded timeout; prefer shared constant & double-check the required condition name

wait_for_condition is invoked with a literal timeout=240.
For consistency with the rest of the file (Timeout.TIMEOUT_1MIN, Timeout.TIMEOUT_2MIN), use the corresponding constant (e.g. Timeout.TIMEOUT_4MIN) or add one if it doesn’t exist. This avoids magic numbers and keeps all timeouts centrally tunable.

Additionally, verify that the CR actually exposes a "HealthCheck" condition—most OCP-style CRDs use "Ready". An incorrect condition name will cause an unnecessary 4-minute stall followed by a failure.

-        llama_stack_distribution.wait_for_condition(condition="HealthCheck", status="True", timeout=240)
+        llama_stack_distribution.wait_for_condition(
+            condition="HealthCheck",  # confirm this is the correct condition
+            status="True",
+            timeout=Timeout.TIMEOUT_4MIN,  # or introduce a constant equal to 240 s
+        )
📜 Review details

Configuration used: .coderabbit.yaml
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between b1a2d7f and aa12fc9.

📒 Files selected for processing (1)
  • tests/rag/conftest.py (1 hunks)
🧰 Additional context used
🧠 Learnings (3)
📓 Common learnings
Learnt from: israel-hdez
PR: opendatahub-io/opendatahub-tests#346
File: tests/model_serving/model_server/inference_graph/conftest.py:85-92
Timestamp: 2025-06-11T16:40:11.593Z
Learning: The helper `create_isvc` (used in tests/model_serving utilities) already waits until the created InferenceService reports Condition READY=True before returning, so additional readiness waits in fixtures are unnecessary.
Learnt from: jiripetrlik
PR: opendatahub-io/opendatahub-tests#335
File: tests/rag/test_rag.py:0-0
Timestamp: 2025-06-19T14:32:17.658Z
Learning: The `wait_for_replicas()` method from ocp_resources.deployment.Deployment raises an exception when timeout is reached rather than returning a boolean value, so it doesn't need explicit return value checking in tests.
Learnt from: jiripetrlik
PR: opendatahub-io/opendatahub-tests#335
File: tests/rag/test_rag.py:0-0
Timestamp: 2025-06-19T14:32:17.658Z
Learning: The `wait_for_replicas()` method from ocp_resources.deployment.Deployment raises an exception when timeout is reached rather than returning a boolean value, so it doesn't need explicit return value checking in tests.
📚 Learning: the helper `create_isvc` (used in tests/model_serving utilities) already waits until the created inf...
Learnt from: israel-hdez
PR: opendatahub-io/opendatahub-tests#346
File: tests/model_serving/model_server/inference_graph/conftest.py:85-92
Timestamp: 2025-06-11T16:40:11.593Z
Learning: The helper `create_isvc` (used in tests/model_serving utilities) already waits until the created InferenceService reports Condition READY=True before returning, so additional readiness waits in fixtures are unnecessary.

Applied to files:

  • tests/rag/conftest.py
📚 Learning: the `wait_for_replicas()` method from ocp_resources.deployment.deployment raises an exception when t...
Learnt from: jiripetrlik
PR: opendatahub-io/opendatahub-tests#335
File: tests/rag/test_rag.py:0-0
Timestamp: 2025-06-19T14:32:17.658Z
Learning: The `wait_for_replicas()` method from ocp_resources.deployment.Deployment raises an exception when timeout is reached rather than returning a boolean value, so it doesn't need explicit return value checking in tests.

Applied to files:

  • tests/rag/conftest.py

@rhods-ci-bot rhods-ci-bot added the Verified Verified pr in Jenkins label Aug 1, 2025
@dbasunag dbasunag merged commit e33c4ad into opendatahub-io:main Aug 1, 2025
9 of 10 checks passed
@github-actions
Copy link
Copy Markdown

github-actions bot commented Aug 1, 2025

Status of building tag latest: success.
Status of pushing tag latest to image registry: success.

@jgarciao
Copy link
Copy Markdown
Contributor Author

jgarciao commented Aug 1, 2025

/cherry-pick 2.23

rhods-ci-bot pushed a commit that referenced this pull request Aug 1, 2025
Fixes timing issue when the LlamaStackDistribition is not ready, causing
the llama-stack service portforwarding to fail

Signed-off-by: Jorge Garcia Oncins <jgarciao@redhat.com>
@rhods-ci-bot
Copy link
Copy Markdown
Contributor

Cherry pick action created PR #482 successfully 🎉!
See: https://github.com/opendatahub-io/opendatahub-tests/actions/runs/16676251980

dbasunag pushed a commit that referenced this pull request Aug 1, 2025
Fixes timing issue when the LlamaStackDistribition is not ready, causing
the llama-stack service portforwarding to fail

Signed-off-by: Jorge Garcia Oncins <jgarciao@redhat.com>
Co-authored-by: Jorge <jgarciao@users.noreply.github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants