Skip to content
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

Merged
merged 7 commits into from
Jan 10, 2025
Merged

[chore] fix test expectations #1601

merged 7 commits into from
Jan 10, 2025

Conversation

atoulme
Copy link
Contributor

@atoulme atoulme commented Jan 10, 2025

Fix expectations - functional tests were not running and fell behind on expectations from testing.

@atoulme atoulme requested review from a team as code owners January 10, 2025 00:21
@atoulme atoulme mentioned this pull request Jan 10, 2025
@@ -13,9 +13,6 @@ metadata:
release: {{ .Release.Name }}
heritage: {{ .Release.Service }}
app.kubernetes.io/component: otel-operator
annotations:
Copy link
Collaborator

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

Copy link
Contributor Author

@atoulme atoulme Jan 10, 2025

Choose a reason for hiding this comment

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

Copy link
Contributor Author

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
        	            		```

@atoulme atoulme merged commit 97cf06d into main Jan 10, 2025
61 of 64 checks passed
@atoulme atoulme deleted the fix_expectations branch January 10, 2025 00:55
@github-actions github-actions bot locked and limited conversation to collaborators Jan 10, 2025
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants