[DNM] Debug KUTTL tests (0.7.0) migration - #61
Conversation
This reverts commit 581680f.
This reverts commit 52e77fb.
Lightspeed-stack version 0.7.0 updates it's llama-stack dependency version to ogx version 1.0.2 [1] in commit 6e5a4e6aed30cc6fa430679746ea17659468ff7e, which breaks us because there have been many changes in the llama-stack/OGX configuration file. Changes that breaks us, that this commit fixes, and the commit hash where they were introduced in the OGX project: - Changed `llama stack run` with `ogx run` [2162e860568132cfe13f4d1e7d5466d9882ba3cf] - Replaced `rag-runtime` with `file-search` [f979c4b00219de2f93e3f60f655f7e5e2cf51d9f] - Replaced `builtin::rag` to `builtin::file_search` [f979c4b00219de2f93e3f60f655f7e5e2cf51d9f] - Replaced `agents` with `responses` [f30e4863096b94eed89f08c5438f1ad9a9068a48] - Replaced `meta-reference` with `builtin` [236a23076ded819004c59f3a7fc67ae5a83cf195] - Removed `safety` api [5ad4753869a145bb0b618a1d3cf6969808cb4435] - Update the DB name from `llamastack` to `ogx` [1]: lightspeed-core/lightspeed-stack#2293
We have references to llama stack in directory names, resources, containers, etc., but it's no longer llama stack, it's ogx now. Change most of these references to ogx.
Lightspeed-stack v0.7.0 introduced OTEL anonymization, since they called the anonymize_value() function unconditionally we get a ValueError exception. To avoid getting that exception we need to set either OTEL_ANONYMIZATION_SECRET or set OTEL_SDK_DISABLED to "true". Since our operator is already disabling telemetry in the OGX config (`telemetry: enabled: false`), we'll set `OTEL_SDK_DISABLED=true` on the lightspeed-stack container.
The go-install-tool macro was letting Go auto-switch to a lower toolchain when installing tools (e.g. govulncheck built with Go 1.25 instead of 1.26), causing failures when analyzing packages that require the newer version. Pin GOTOOLCHAIN and encode the Go version in cached binary names so toolchain upgrades trigger automatic rebuilds. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
This allows us to gather the logs using must-gather from the exact point when the tests fail.
|
Skipping CI for Draft Pull Request. |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: lpiwowar The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
|
Important Review skippedDraft detected. Please check the settings in the CodeRabbit UI or the ⚙️ Run configurationConfiguration used: Central YAML (base), Organization UI (inherited) Review profile: CHILL Plan: Enterprise Run ID: You can disable this status message by setting the Use the checkbox below for a quick retry:
Comment |
lpiwowar
changed the title
|
/test all |
|
@lpiwowar: The following test failed, say
Full PR test history. Your PR dashboard. DetailsInstructions 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. |
2 participants
No description provided.