Fix bug in compatibility version script: kubelet not upgraded #35948
+1
−1
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Noticed a warning message in the upgrade script:
On further inspection, find returns two variables that get passed to docker cp which causes an error.
Even in the logs of successful runs (https://storage.googleapis.com/kubernetes-ci-logs/logs/ci-kubernetes-e2e-kind-two-steps-upgrade-n-minus-1/1991867497766195200/build-log.txt), "Updated kubelet" never appears in the logs.
This addresses an orthogonal issue that isn't directly tied to the flake
/hold