Fix kubectl cp failure with wildcard #6387
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
antoninbas
reviewed
May 31, 2024
Signed-off-by: Lan Luo <luola@vmware.com>
luolanzone
force-pushed
the
fix-coverage-cp
branch
from
efcb2ae
to
565f34e
Compare
luolanzone
added
the
size/S
|
/test-multicluster-e2e |
1 similar comment
|
/test-multicluster-e2e |
antoninbas
approved these changes
Jun 3, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
It turns out kubectl cp with wildcard is not working properly. I saw following errors in our CI jobs:
Fix it by check all files on /tmp/coverage/ and copy them one by one.
Here is some discussion about the kubectl cp bug.
https://devops.stackexchange.com/questions/6669/copy-multiple-files-using-wildcard-from-kubernetes-container