-
Notifications
You must be signed in to change notification settings - Fork 152
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.
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
[chore] fix test expectations #1601
Conversation
0acda7e
to
75a2405
Compare
1d2607d
to
cc733c2
Compare
@@ -13,9 +13,6 @@ metadata: | |||
release: {{ .Release.Name }} | |||
heritage: {{ .Release.Service }} | |||
app.kubernetes.io/component: otel-operator | |||
annotations: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
can we keep these in until we make the crd changes in the chart? it should still be okay to run this hook with the test install
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
No, tests fail if we leave this hook. See https://github.com/signalfx/splunk-otel-collector-chart/actions/runs/12700626921/job/35403663872
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
collector/templates/operator/instrumentation.yaml failed: 1 error occurred:
* Internal error occurred: failed calling webhook "minstrumentation.kb.io": failed to call webhook: Post "[https://sock-operator-webhook.default.svc:443/mutate-opentelemetry-io-v1alpha1-instrumentation?timeout=10s](https://sock-operator-webhook.default.svc/mutate-opentelemetry-io-v1alpha1-instrumentation?timeout=10s)": dial tcp 10.96.242.75:443: connect: connection refused
functional_test.go:300:
Error Trace: /home/runner/work/splunk-otel-collector-chart/splunk-otel-collector-chart/functional_tests/functional_test.go:300
/home/runner/work/splunk-otel-collector-chart/splunk-otel-collector-chart/functional_tests/functional_test.go:119
/opt/hostedtoolcache/go/1.22.10/x64/src/sync/once.go:74
/opt/hostedtoolcache/go/1.22.10/x64/src/sync/once.go:65
/home/runner/work/splunk-otel-collector-chart/splunk-otel-collector-chart/functional_tests/functional_test.go:98
/home/runner/work/splunk-otel-collector-chart/splunk-otel-collector-chart/functional_tests/functional_test.go:581
Error: Received unexpected error:
post-upgrade hooks failed: warning: Hook post-upgrade splunk-otel-collector/templates/operator/instrumentation.yaml failed: 1 error occurred:
* Internal error occurred: failed calling webhook "minstrumentation.kb.io": failed to call webhook: Post "[https://sock-operator-webhook.default.svc:443/mutate-opentelemetry-io-v1alpha1-instrumentation?timeout=10s](https://sock-operator-webhook.default.svc/mutate-opentelemetry-io-v1alpha1-instrumentation?timeout=10s)": dial tcp 10.96.242.75:443: connect: connection refused
```
Fix expectations - functional tests were not running and fell behind on expectations from testing.