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
Bug 1990014: Use cmd for Windows pods #907
Bug 1990014: Use cmd for Windows pods #907
Conversation
@deejross: This pull request references Bugzilla bug 1990014, which is valid. The bug has been moved to the POST state. The bug has been updated to refer to the pull request using the external bug tracker. 3 validation(s) were run on this bug
Requesting review from QA contact: In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
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.
Thanks for working on this, @deejross
pkg/cli/debug/debug.go
Outdated
@@ -62,6 +62,9 @@ const ( | |||
containerResourcesAnnotationPrefix = "resources.workload.openshift.io/" | |||
// podWorkloadTargetAnnotationPrefix contains the prefix for the pod workload target annotation | |||
podWorkloadTargetAnnotationPrefix = "target.workload.openshift.io/" | |||
kubeOSNodeSelector = "kubernetes.io/os" | |||
commandLinuxShell = "/bin/sh" | |||
commandWindowsShell = "powershell" |
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.
It is risky to use powershell.exe
. In certain Windows container images, the binary is pwsh.exe
. I suggest using cmd.exe (the older command interpreter) which is guaranteed to exist in all Windows container images.
/restest-required |
/retest-required |
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.
/lgtm
/approve
/override ci/prow/e2e-agnostic-cmd
unrelated failure and we're actively working on improving the reliability of that test suite.
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: deejross, soltysh 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 |
@soltysh: Overrode contexts on behalf of soltysh: ci/prow/e2e-agnostic-cmd In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
/retest-required Please review the full test history for this PR and help us cut down flakes. |
1 similar comment
/retest-required Please review the full test history for this PR and help us cut down flakes. |
@deejross: All pull requests linked via external trackers have merged: Bugzilla bug 1990014 has been moved to the MODIFIED state. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
/cherry-pick release-4.8 |
@deejross: #907 failed to apply on top of branch "release-4.8":
In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
No description provided.