Azure windows-2019 builds failing: can't start sshd

[mboersma]

The pull-azure-vhds and pull-azure-sigs jobs have begun to fail consistently because of the windows-2019 targets:

�[0;32m    azure-arm.sig-windows-2019-containerd: TASK [systemprep : Enable ssh login without a password] ************************�[0m
�[0;32m    azure-arm.sig-windows-2019-containerd: changed: [default]�[0m
�[0;32m    azure-arm.sig-windows-2019-containerd:�[0m
�[0;32m    azure-arm.sig-windows-2019-containerd: TASK [systemprep : Set SSH service startup mode to auto and ensure it is started] ***�[0m
�[0;32m    azure-arm.sig-windows-2019-containerd: An exception occurred during task execution. To see the full traceback, use -vvv. The error was: at <ScriptBlock>, <No file>: line 1064�[0m
�[0;32m    azure-arm.sig-windows-2019-containerd: fatal: [default]: FAILED! => {"changed": false, "msg": "Unhandled exception while executing module: Service 'OpenSSH SSH Server (sshd)' cannot be started due to the following error: Cannot start service sshd on computer '.'."}�[0m
�[0;32m    azure-arm.sig-windows-2019-containerd:�[0m
�[0;32m    azure-arm.sig-windows-2019-containerd: PLAY RECAP *********************************************************************�[0m
�[0;32m    azure-arm.sig-windows-2019-containerd: default                    : ok=19   changed=15   unreachable=0    failed=1    skipped=9    rescued=0    ignored=0�[0m

This is blocking CI and keeping PRs from merging, so we may want to skip this test for now unless a solution is iminent.

Environment

• Make target: make build-azure-vhd-windows-2019 or make build-azure-sig-windows-2019

---

/kind bug

[k8s-triage-robot]

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

This bot triages un-triaged issues 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 as fresh with /remove-lifecycle stale
• Close this issue with /close
• Offer to help out with Issue Triage

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

/lifecycle stale