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

Bump OpenTelemetry libs #2686

Merged
merged 1 commit into from
Dec 21, 2023
Merged

Conversation

jsafrane
Copy link
Contributor

@jsafrane jsafrane commented Dec 8, 2023

Bump especially
go.opentelemetry.io/contrib/instrumentation/net/http/otelhttp and go.opentelemetry.io/contrib/instrumentation/google.golang.org/grpc/otelgrpc to v0.46 to fix CVE-2023-47108.

The rest of lib updates were required by the new otelhttp. Please review + test carefully, there are quite large jumps between versions.

Release note:

NONE 

@k8s-ci-robot k8s-ci-robot added the cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. label Dec 8, 2023
@k8s-ci-robot k8s-ci-robot added the size/L Denotes a PR that changes 100-499 lines, ignoring generated files. label Dec 8, 2023
@adikul30
Copy link
Contributor

/ok-to-test

@k8s-ci-robot k8s-ci-robot added the ok-to-test Indicates a non-member PR verified by an org member that is safe to test. label Dec 11, 2023
@svcbot-qecnsdp
Copy link

Started vanilla Block pipeline... Build Number: 2398

@svcbot-qecnsdp
Copy link

Block vanilla build status: FAILURE 
Stage before exit: e2e-tests 
Jenkins E2E Test Results: 
------------------------------

Ran 1 of 809 Specs in 404.931 seconds
SUCCESS! -- 1 Passed | 0 Failed | 0 Pending | 808 Skipped
PASS

Ginkgo ran 1 suite in 7m45.703859566s
Test Suite Passed
--
Ran 14 of 809 Specs in 6354.230 seconds
FAIL! -- 13 Passed | 1 Failed | 0 Pending | 795 Skipped
--- FAIL: TestE2E (6354.30s)
FAIL

Ginkgo ran 1 suite in 1h46m10.281749274s

Test Suite Failed

@svcbot-qecnsdp
Copy link

Started vanilla Block pipeline... Build Number: 2400

@svcbot-qecnsdp
Copy link

Block vanilla build status: FAILURE 
Stage before exit: e2e-tests 
Jenkins E2E Test Results: 
------------------------------

Ran 1 of 809 Specs in 371.192 seconds
SUCCESS! -- 1 Passed | 0 Failed | 0 Pending | 808 Skipped
PASS

Ginkgo ran 1 suite in 7m25.776198853s
Test Suite Passed
--
Ran 14 of 809 Specs in 7268.668 seconds
FAIL! -- 13 Passed | 1 Failed | 0 Pending | 795 Skipped
--- FAIL: TestE2E (7268.75s)
FAIL

Ginkgo ran 1 suite in 2h1m25.42014378s

Test Suite Failed

@svcbot-qecnsdp
Copy link

Started vanilla Block pipeline... Build Number: 2403

@svcbot-qecnsdp
Copy link

Block vanilla build status: FAILURE 
Stage before exit: e2e-tests 
Jenkins E2E Test Results: 
------------------------------

Ran 1 of 809 Specs in 377.271 seconds
SUCCESS! -- 1 Passed | 0 Failed | 0 Pending | 808 Skipped
PASS

Ginkgo ran 1 suite in 7m35.236718965s
Test Suite Passed
--
Ran 14 of 809 Specs in 7938.312 seconds
FAIL! -- 8 Passed | 6 Failed | 0 Pending | 795 Skipped
--- FAIL: TestE2E (7938.42s)
FAIL

Ginkgo ran 1 suite in 2h12m35.703028883s

Test Suite Failed

@jsafrane
Copy link
Contributor Author

@adikul30, can I please get more details about the failed tests? What failed and how? How can I re-run the failed test by myself?

And, do you have any govet or lint tests? Those could be affected by this PR too.

@adikul30
Copy link
Contributor

@adikul30, can I please get more details about the failed tests? What failed and how? How can I re-run the failed test by myself?

And, do you have any govet or lint tests? Those could be affected by this PR too.

@jsafrane, I've run tests tagged with 'csi-block-vanilla'. These tests can be found in the tests/e2e directory. A new cluster is provisioned on internal test infra and these tests are run on the cluster. The test links are private and won't be accessible to those outside the company. So, currently I don't think there's a way for an external contributor to find out what went wrong. The command jtest block-vanilla on this PR should run the same tests I've executed. I don't see it's been used in a while. Can you give this command a try? cc: @sashrith

govet is run as part of linter check (https://github.com/kubernetes-sigs/vsphere-csi-driver/blob/master/.golangci.yml#L6). Since this PR doesn't have any go code changes, I think those won't be executed. Can you please run make check locally and provide an output for that?

@svcbot-qecnsdp
Copy link

Started vanilla Block pipeline... Build Number: 2409

@svcbot-qecnsdp
Copy link

Block vanilla build status: FAILURE 
Stage before exit: e2e-tests 
Jenkins E2E Test Results: 
------------------------------

Ran 1 of 809 Specs in 569.236 seconds
SUCCESS! -- 1 Passed | 0 Failed | 0 Pending | 808 Skipped
PASS

Ginkgo ran 1 suite in 10m51.115927718s
Test Suite Passed
--
Ran 14 of 809 Specs in 8491.819 seconds
FAIL! -- 7 Passed | 7 Failed | 0 Pending | 795 Skipped
--- FAIL: TestE2E (8491.93s)
FAIL

Ginkgo ran 1 suite in 2h21m49.371922905s

Test Suite Failed

@jsafrane
Copy link
Contributor Author

govet is run as part of linter check (https://github.com/kubernetes-sigs/vsphere-csi-driver/blob/master/.golangci.yml#L6). Since this PR doesn't have any go code changes, I think those won't be executed.

This PR brings >600 changed files in the imported packages, I think that's quite a big code change :-).
make check passed:

make check
hack/check-format.sh
hack/check-mdlint.sh
hack/check-shell.sh
hack/check-staticcheck.sh
+ go version
go version go1.21.3 linux/amd64
++ dirname hack/check-staticcheck.sh
+ cd hack/..
+ go install honnef.co/go/tools/cmd/[email protected]
++ go env GOPATH
+ GOOS=linux
+ /home/jsafrane/project/go/bin/staticcheck --version
staticcheck 2023.1 (v0.4.0)
++ go env GOPATH
++ go list ./...
++ grep -v /vendor/
+ GOOS=linux
+ /home/jsafrane/project/go/bin/staticcheck sigs.k8s.io/vsphere-csi-driver/v3/cmd/syncer sigs.k8s.io/vsphere-csi-driver/v3/cmd/vsphere-csi sigs.k8s.io/vsphere-csi-driver/v3/pkg/apis/cnsoperator sigs.k8s.io/vsphere-csi-driver/v3/pkg/apis/cnsoperator/cnsfileaccessconfig/v1alpha1 sigs.k8s.io/vsphere-csi-driver/v3/pkg/apis/cnsoperator/cnsnodevmattachment/v1alpha1 sigs.k8s.io/vsphere-csi-driver/v3/pkg/apis/cnsoperator/cnsregistervolume/v1alpha1 sigs.k8s.io/vsphere-csi-driver/v3/pkg/apis/cnsoperator/cnsvolumemetadata/v1alpha1 sigs.k8s.io/vsphere-csi-driver/v3/pkg/apis/cnsoperator/config sigs.k8s.io/vsphere-csi-driver/v3/pkg/apis/cnsoperator/storagepolicy/v1alpha1 sigs.k8s.io/vsphere-csi-driver/v3/pkg/apis/migration sigs.k8s.io/vsphere-csi-driver/v3/pkg/apis/migration/config sigs.k8s.io/vsphere-csi-driver/v3/pkg/apis/migration/v1alpha1 sigs.k8s.io/vsphere-csi-driver/v3/pkg/apis/storagepool sigs.k8s.io/vsphere-csi-driver/v3/pkg/apis/storagepool/cns sigs.k8s.io/vsphere-csi-driver/v3/pkg/apis/storagepool/cns/v1alpha1 sigs.k8s.io/vsphere-csi-driver/v3/pkg/apis/storagepool/config sigs.k8s.io/vsphere-csi-driver/v3/pkg/common/cns-lib/node sigs.k8s.io/vsphere-csi-driver/v3/pkg/common/cns-lib/volume sigs.k8s.io/vsphere-csi-driver/v3/pkg/common/cns-lib/vsphere sigs.k8s.io/vsphere-csi-driver/v3/pkg/common/config sigs.k8s.io/vsphere-csi-driver/v3/pkg/common/fault sigs.k8s.io/vsphere-csi-driver/v3/pkg/common/prometheus sigs.k8s.io/vsphere-csi-driver/v3/pkg/common/unittestcommon sigs.k8s.io/vsphere-csi-driver/v3/pkg/common/utils sigs.k8s.io/vsphere-csi-driver/v3/pkg/csi/service sigs.k8s.io/vsphere-csi-driver/v3/pkg/csi/service/common sigs.k8s.io/vsphere-csi-driver/v3/pkg/csi/service/common/commonco sigs.k8s.io/vsphere-csi-driver/v3/pkg/csi/service/common/commonco/k8sorchestrator sigs.k8s.io/vsphere-csi-driver/v3/pkg/csi/service/common/commonco/types sigs.k8s.io/vsphere-csi-driver/v3/pkg/csi/service/common/placementengine sigs.k8s.io/vsphere-csi-driver/v3/pkg/csi/service/logger sigs.k8s.io/vsphere-csi-driver/v3/pkg/csi/service/mounter sigs.k8s.io/vsphere-csi-driver/v3/pkg/csi/service/osutils sigs.k8s.io/vsphere-csi-driver/v3/pkg/csi/service/vanilla sigs.k8s.io/vsphere-csi-driver/v3/pkg/csi/service/wcp sigs.k8s.io/vsphere-csi-driver/v3/pkg/csi/service/wcpguest sigs.k8s.io/vsphere-csi-driver/v3/pkg/csi/types sigs.k8s.io/vsphere-csi-driver/v3/pkg/internalapis sigs.k8s.io/vsphere-csi-driver/v3/pkg/internalapis/cnsoperator/cnsfilevolumeclient sigs.k8s.io/vsphere-csi-driver/v3/pkg/internalapis/cnsoperator/cnsfilevolumeclient/v1alpha1 sigs.k8s.io/vsphere-csi-driver/v3/pkg/internalapis/cnsoperator/config sigs.k8s.io/vsphere-csi-driver/v3/pkg/internalapis/cnsoperator/triggercsifullsync/v1alpha1 sigs.k8s.io/vsphere-csi-driver/v3/pkg/internalapis/cnsvolumeinfo sigs.k8s.io/vsphere-csi-driver/v3/pkg/internalapis/cnsvolumeinfo/config sigs.k8s.io/vsphere-csi-driver/v3/pkg/internalapis/cnsvolumeinfo/v1alpha1 sigs.k8s.io/vsphere-csi-driver/v3/pkg/internalapis/cnsvolumeoperationrequest sigs.k8s.io/vsphere-csi-driver/v3/pkg/internalapis/cnsvolumeoperationrequest/config sigs.k8s.io/vsphere-csi-driver/v3/pkg/internalapis/cnsvolumeoperationrequest/v1alpha1 sigs.k8s.io/vsphere-csi-driver/v3/pkg/internalapis/csinodetopology sigs.k8s.io/vsphere-csi-driver/v3/pkg/internalapis/csinodetopology/config sigs.k8s.io/vsphere-csi-driver/v3/pkg/internalapis/csinodetopology/v1alpha1 sigs.k8s.io/vsphere-csi-driver/v3/pkg/internalapis/featurestates sigs.k8s.io/vsphere-csi-driver/v3/pkg/internalapis/featurestates/config sigs.k8s.io/vsphere-csi-driver/v3/pkg/internalapis/featurestates/v1alpha1 sigs.k8s.io/vsphere-csi-driver/v3/pkg/kubernetes sigs.k8s.io/vsphere-csi-driver/v3/pkg/syncer sigs.k8s.io/vsphere-csi-driver/v3/pkg/syncer/admissionhandler sigs.k8s.io/vsphere-csi-driver/v3/pkg/syncer/cnsoperator/controller sigs.k8s.io/vsphere-csi-driver/v3/pkg/syncer/cnsoperator/controller/cnsfileaccessconfig sigs.k8s.io/vsphere-csi-driver/v3/pkg/syncer/cnsoperator/controller/cnsnodevmattachment sigs.k8s.io/vsphere-csi-driver/v3/pkg/syncer/cnsoperator/controller/cnsregistervolume sigs.k8s.io/vsphere-csi-driver/v3/pkg/syncer/cnsoperator/controller/cnsvolumemetadata sigs.k8s.io/vsphere-csi-driver/v3/pkg/syncer/cnsoperator/controller/csinodetopology sigs.k8s.io/vsphere-csi-driver/v3/pkg/syncer/cnsoperator/controller/triggercsifullsync sigs.k8s.io/vsphere-csi-driver/v3/pkg/syncer/cnsoperator/manager sigs.k8s.io/vsphere-csi-driver/v3/pkg/syncer/cnsoperator/types sigs.k8s.io/vsphere-csi-driver/v3/pkg/syncer/cnsoperator/util sigs.k8s.io/vsphere-csi-driver/v3/pkg/syncer/k8scloudoperator sigs.k8s.io/vsphere-csi-driver/v3/pkg/syncer/storagepool sigs.k8s.io/vsphere-csi-driver/v3/tests/e2e
hack/check-vet.sh
hack/check-golangci-lint.sh
golangci/golangci-lint info checking GitHub for tag 'v1.55.1'
golangci/golangci-lint info found version: 1.55.1 for v1.55.1/linux/amd64
golangci/golangci-lint info installed /home/jsafrane/project/go/bin/golangci-lint
INFO [config_reader] Config search paths: [./ /home/jsafrane/project/go/src/sigs.k8s.io/vsphere-csi-driver /home/jsafrane/project/go/src/sigs.k8s.io /home/jsafrane/project/go/src /home/jsafrane/project/go /home/jsafrane/project /home/jsafrane /home /] 
INFO [config_reader] Used config file .golangci.yml 
INFO [lintersdb] Active 8 linters: [errcheck gosimple govet ineffassign lll misspell staticcheck unused] 
INFO [loader] Go packages loading at mode 575 (files|types_sizes|compiled_files|deps|exports_file|imports|name) took 598.311835ms 
INFO [runner/filename_unadjuster] Pre-built 0 adjustments in 163.158897ms 
INFO [linters_context/goanalysis] analyzers took 11m59.032528365s with top 10 stages: buildir: 8m47.791397823s, nilness: 21.852603687s, S1038: 9.992615522s, inspect: 7.3149234s, misspell: 6.142945271s, fact_purity: 5.151390915s, printf: 5.061888717s, typedness: 4.661401307s, ctrlflow: 4.31060802s, fact_deprecated: 4.170730207s 
INFO [runner] Issues before processing: 127, after processing: 0 
INFO [runner] Processors filtering stat (out/in): path_prettifier: 127/127, nolint: 0/1, exclude: 37/37, exclude-rules: 1/37, cgo: 127/127, filename_unadjuster: 127/127, skip_dirs: 127/127, autogenerated_exclude: 37/127, skip_files: 127/127, identifier_marker: 37/37 
INFO [runner] processing took 36.048293ms with stages: nolint: 33.259671ms, identifier_marker: 1.057563ms, autogenerated_exclude: 672.713µs, path_prettifier: 628.505µs, skip_dirs: 210.664µs, exclude-rules: 187.619µs, cgo: 16.663µs, filename_unadjuster: 8.46µs, max_same_issues: 1.833µs, uniq_by_line: 933ns, max_from_linter: 558ns, skip_files: 481ns, fixer: 459ns, diff: 342ns, exclude: 330ns, sort_results: 305ns, source_code: 293ns, max_per_file_from_linter: 289ns, severity-rules: 259ns, path_shortener: 228ns, path_prefixer: 125ns 
INFO [runner] linters took 1m10.744206313s with stages: goanalysis_metalinter: 1m10.707965908s 
INFO File cache stats: 317 entries of total size 6.7MiB 
INFO Memory: 593 samples, avg is 3128.5MB, max is 4505.5MB 
INFO Execution took 1m11.511059895s               

@jsafrane
Copy link
Contributor Author

rebased

@svcbot-qecnsdp
Copy link

Started vanilla Block pipeline... Build Number: 2412

@svcbot-qecnsdp
Copy link

Block vanilla build status: FAILURE 
Stage before exit: e2e-tests 
Jenkins E2E Test Results: 
------------------------------

Ran 1 of 809 Specs in 402.685 seconds
SUCCESS! -- 1 Passed | 0 Failed | 0 Pending | 808 Skipped
PASS

Ginkgo ran 1 suite in 7m48.628562446s
Test Suite Passed
--
Ran 14 of 809 Specs in 6937.765 seconds
FAIL! -- 12 Passed | 2 Failed | 0 Pending | 795 Skipped
--- FAIL: TestE2E (6937.85s)
FAIL

Ginkgo ran 1 suite in 1h55m55.231005914s

Test Suite Failed

@jsafrane
Copy link
Contributor Author

@adikul30 how shall we proceed here? I can't fix any e2e errors that I don't see.

@svcbot-qecnsdp
Copy link

Started vanilla Block pipeline... Build Number: 2414

@svcbot-qecnsdp
Copy link

Block vanilla build status: FAILURE 
Stage before exit: testbed-deployment 

@svcbot-qecnsdp
Copy link

Started Vanilla block pre-checkin pipeline... Build Number: 2599

@svcbot-qecnsdp
Copy link

Build ID: 2599
Block vanilla build status: FAILURE 
Stage before exit: e2e-tests 
Jenkins E2E Test Results: 
------------------------------

Ran 1 of 809 Specs in 373.310 seconds
SUCCESS! -- 1 Passed | 0 Failed | 0 Pending | 808 Skipped
PASS

Ginkgo ran 1 suite in 7m50.070877367s
Test Suite Passed
--
Ran 13 of 809 Specs in 7722.878 seconds
FAIL! -- 7 Passed | 6 Failed | 0 Pending | 796 Skipped
--- FAIL: TestE2E (7723.11s)
FAIL

Ginkgo ran 1 suite in 2h9m12.053175039s

Test Suite Failed

@adikul30
Copy link
Contributor

adikul30 commented Dec 19, 2023

I can't fix any e2e errors that I don't see.

Yeah, there's really no way for you to access unless I upload the logs at some place after every test run.

But I ran an individual test that had failed as part of the entire suite and it passed,

Build #2600 (Dec 19, 2023, 11:36:02 AM)
adkulkarni
PR 2686
------------------------------ Ran 1 of 809 Specs in 1615.162 seconds SUCCESS! -- 1 Passed | 0 Failed | 0 Pending | 808 Skipped PASS Ginkgo ran 1 suite in 28m33.053454295s Test Suite Passed 

@jsafrane, the tests seem to be very flaky right now, likely underlying infra issues. Let me check with the team if that's the case and if we can merge your change since I don't see any change related issues in the test.

@svcbot-qecnsdp
Copy link

Started Vanilla block pre-checkin pipeline... Build Number: 2601

@svcbot-qecnsdp
Copy link

Build ID: 2601
Block vanilla build status: FAILURE 
Stage before exit: e2e-tests 
Jenkins E2E Test Results: 
------------------------------

Ran 1 of 809 Specs in 371.505 seconds
SUCCESS! -- 1 Passed | 0 Failed | 0 Pending | 808 Skipped
PASS

Ginkgo ran 1 suite in 7m48.933677096s
Test Suite Passed
--
------------------------------

Ran 13 of 809 Specs in 7124.554 seconds
SUCCESS! -- 13 Passed | 0 Failed | 0 Pending | 796 Skipped
PASS

Ginkgo ran 1 suite in 1h59m11.696343428s
Test Suite Passed
--

Ran 50 of 809 Specs in 614.410 seconds
FAIL! -- 48 Passed | 2 Failed | 0 Pending | 759 Skipped


Ginkgo ran 1 suite in 10m41.679018742s

Test Suite Failed

@jsafrane
Copy link
Contributor Author

@adikul30 other CVE PRs do not need to go through "Vanilla block pre-checkin pipeline": #2714

@adikul30
Copy link
Contributor

adikul30 commented Dec 20, 2023

@adikul30 other CVE PRs do not need to go through "Vanilla block pre-checkin pipeline": #2714

Ideally, we should be running at least one of the regression pipelines for every change.

But, I see almost all tests passed in the last run. I'll get this change checked-in today.

@svcbot-qecnsdp
Copy link

Started Vanilla block pre-checkin pipeline... Build Number: 2603

@svcbot-qecnsdp
Copy link

Build ID: 2603
Block vanilla build status: FAILURE 
Stage before exit: e2e-tests 
Jenkins E2E Test Results: 
Ran 2 of 809 Specs in 250.454 seconds
FAIL! -- 1 Passed | 1 Failed | 0 Pending | 807 Skipped
--- FAIL: TestE2E (250.52s)
FAIL

Ginkgo ran 1 suite in 5m19.60542767s

Test Suite Failed

@svcbot-qecnsdp
Copy link

Started Vanilla block pre-checkin pipeline... Build Number: 2604

kind: CustomResourceDefinition
metadata:
annotations:
controller-gen.kubebuilder.io/version: v0.6.2
Copy link
Member

Choose a reason for hiding this comment

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

why do we need to change version from v0.6.2 to v0.2.5?
Also we are moving back to apiextensions.k8s.io/v1beta1from apiextensions.k8s.io/v1?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Good catch, I had an old controller-gen. Fixed now.

@svcbot-qecnsdp
Copy link

Build ID: 2604
Block vanilla build status: SUCCESS 
Stage before exit: e2e-tests 
Jenkins E2E Test Results: 
------------------------------

Ran 1 of 809 Specs in 100.267 seconds
SUCCESS! -- 1 Passed | 0 Failed | 0 Pending | 808 Skipped
PASS

Ginkgo ran 1 suite in 2m49.596315036s
Test Suite Passed

Bump especially
go.opentelemetry.io/contrib/instrumentation/net/http/otelhttp and go.opentelemetry.io/contrib/instrumentation/google.golang.org/grpc/otelgrpc
to v0.46 to fix CVE-2023-47108.

The rest of OpenTelemetry lib updates were required by the new otelhttp.
Copy link
Member

@divyenpatel divyenpatel left a comment

Choose a reason for hiding this comment

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

/approve
/lgtm

@k8s-ci-robot
Copy link
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: divyenpatel, jsafrane

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@k8s-ci-robot k8s-ci-robot added lgtm "Looks good to me", indicates that a PR is ready to be merged. approved Indicates a PR has been approved by an approver from all required OWNERS files. labels Dec 21, 2023
@k8s-ci-robot k8s-ci-robot merged commit 2cbbd87 into kubernetes-sigs:master Dec 21, 2023
8 checks passed
jsafrane added a commit to jsafrane/vsphere-csi-driver that referenced this pull request Jan 3, 2024
Bump especially
go.opentelemetry.io/contrib/instrumentation/net/http/otelhttp and go.opentelemetry.io/contrib/instrumentation/google.golang.org/grpc/otelgrpc
to v0.46 to fix CVE-2023-47108.

The rest of OpenTelemetry lib updates were required by the new otelhttp.
jsafrane added a commit to jsafrane/vsphere-csi-driver that referenced this pull request Jan 4, 2024
Bump especially
go.opentelemetry.io/contrib/instrumentation/net/http/otelhttp and go.opentelemetry.io/contrib/instrumentation/google.golang.org/grpc/otelgrpc
to v0.46 to fix CVE-2023-47108.

The rest of OpenTelemetry lib updates were required by the new otelhttp.
jsafrane added a commit to jsafrane/vsphere-csi-driver that referenced this pull request Jan 5, 2024
Bump especially
go.opentelemetry.io/contrib/instrumentation/net/http/otelhttp and go.opentelemetry.io/contrib/instrumentation/google.golang.org/grpc/otelgrpc
to v0.46 to fix CVE-2023-47108.

The rest of OpenTelemetry lib updates were required by the new otelhttp.
gnufied pushed a commit to gnufied/vsphere-csi-driver that referenced this pull request Jan 22, 2024
Bump especially
go.opentelemetry.io/contrib/instrumentation/net/http/otelhttp and go.opentelemetry.io/contrib/instrumentation/google.golang.org/grpc/otelgrpc
to v0.46 to fix CVE-2023-47108.

The rest of OpenTelemetry lib updates were required by the new otelhttp.
gnufied pushed a commit to gnufied/vsphere-csi-driver that referenced this pull request May 31, 2024
Bump especially
go.opentelemetry.io/contrib/instrumentation/net/http/otelhttp and go.opentelemetry.io/contrib/instrumentation/google.golang.org/grpc/otelgrpc
to v0.46 to fix CVE-2023-47108.

The rest of OpenTelemetry lib updates were required by the new otelhttp.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
approved Indicates a PR has been approved by an approver from all required OWNERS files. cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. lgtm "Looks good to me", indicates that a PR is ready to be merged. ok-to-test Indicates a non-member PR verified by an org member that is safe to test. size/L Denotes a PR that changes 100-499 lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants