Skip to content

OTel kuttl test fix: add bad psql command to force an error and ensur… #4425

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
dsessler7 merged 2 commits into from
Feb 16, 2026
+5 −1
Merged

OTel kuttl test fix: add bad psql command to force an error and ensur… #4425

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
d893c0c
OTel kuttl test fix: add bad psql command to force an error and ensur…
dsessler7 Feb 16, 2026
001d753
Pin go version to 1.25 for kuttl github action test (until kuttl supp…
dsessler7 Feb 12, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion .github/workflows/test.yaml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -93,7 +93,7 @@ jobs:
steps:
- uses: actions/checkout@v6
- uses: actions/setup-go@v6
with: { go-version: stable }
with: { go-version: '1.25.x' } # TODO: revert to stable when kuttl supports Go 1.26 (missing testDeps.ModulePath)

- name: Start k3s
uses: ./.github/actions/k3d
Expand Down
4 changes: 4 additions & 0 deletions testing/kuttl/e2e/otel-logging-and-metrics/22-assert-instance.yaml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -4,6 +4,8 @@ commands:
# First, check that all containers in the instance pod are ready.
# Then, grab the collector metrics output and check that a postgres
# metric is present, as well as a patroni metric.
# Then use psql to run a bad command in the database to get an error
# and ensure that there is a postgres log to capture.
# Then, check the collector logs for patroni, and postgres logs.
# Finally, ensure the monitoring user exists and is configured.
- script: |
Expand Down Expand Up @@ -35,6 +37,8 @@ commands:
exit 1
}

kubectl exec "${pod}" -n "${NAMESPACE}" -- psql -c "SHOW DOES_NOT_EXIST;" 2>/dev/null || true

logs=$(kubectl logs "${pod}" --namespace "${NAMESPACE}" -c collector | grep InstrumentationScope)
{ contains "${logs}" 'InstrumentationScope patroni'; } || {
retry "patroni logs not found"
Expand Down
Loading