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

Skipping TestSkaffold on Windows #14232

Open
spowelljr opened this issue May 26, 2022 · 3 comments
Open

Skipping TestSkaffold on Windows #14232

spowelljr opened this issue May 26, 2022 · 3 comments
Labels
co/hyperv HyperV related issues kind/process Process oriented issues, like setting up CI lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. priority/backlog Higher priority than priority/awaiting-more-evidence.

Comments

@spowelljr
Copy link
Member

spowelljr commented May 26, 2022

TestSkaffold on Windows is failing with the following error:

ERROR: rpc error: code = Unknown desc = error getting credentials - err: exit status 1, out: `error getting credentials - err: exit status 1, out: `A specified logon session does not exist. It may already have been terminated.``

This is a known issue (docker/cli#2682) outside of our control.
tl;dr: You cannot Docker login via an elevated shell depending on your environment as it appears the credentials don't get passed through

And with our CI flow we SSH into the Windows machine which starts us in elevated permission and trying to obtain unelevated permission proves much harder than expected and requires complex work arounds.

Also tried to change Jenkins from connecting to the Windows machines from SSH to via a Windows service, however we run into issue with proxies.

So for not just going to skip this test on Windows until we find a better work around.

@spowelljr spowelljr added co/hyperv HyperV related issues priority/backlog Higher priority than priority/awaiting-more-evidence. kind/process Process oriented issues, like setting up CI labels May 26, 2022
@spowelljr spowelljr changed the title Skipping TestSkaffold on Hyper-V Skipping TestSkaffold on Windows May 26, 2022
@vharsh
Copy link
Contributor

vharsh commented May 31, 2022

/close

@k8s-ci-robot
Copy link
Contributor

@vharsh: You can't close an active issue/PR unless you authored it or you are a collaborator.

In response to this:

/close

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.

@k8s-triage-robot
Copy link

The Kubernetes project currently lacks enough contributors to adequately respond to all issues and PRs.

This bot triages issues and PRs according to the following rules:

  • After 90d of inactivity, lifecycle/stale is applied
  • After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
  • After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

  • Mark this issue or PR as fresh with /remove-lifecycle stale
  • Mark this issue or PR as rotten with /lifecycle rotten
  • Close this issue or PR with /close
  • Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

@k8s-ci-robot k8s-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Aug 29, 2022
@spowelljr spowelljr added lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. and removed lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. labels Aug 29, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
co/hyperv HyperV related issues kind/process Process oriented issues, like setting up CI lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. priority/backlog Higher priority than priority/awaiting-more-evidence.
Projects
None yet
Development

No branches or pull requests

4 participants