Uploaded image for project: 'OpenShift Bugs'
  1. OpenShift Bugs
  2. OCPBUGS-56131

Azure Machines inaccessible by SSH

XMLWordPrintable

    • Quality / Stability / Reliability
    • False
    • Hide

      None

      Show
      None
    • 3
    • None
    • None
    • None
    • None
    • WINC - Sprint 275
    • 1
    • In Progress
    • Bug Fix
    • Hide
      Fixes an issue where Windows Server 2019 machines were not having a running SSH server due to network instability.
      This fixes the issue by retrying the SSH server install at VM creation.
      Show
      Fixes an issue where Windows Server 2019 machines were not having a running SSH server due to network instability. This fixes the issue by retrying the SSH server install at VM creation.
    • None
    • None
    • None
    • None

      Description of problem:

      Occasionally in CI, azure VMs are unable to be SSH'd into.

The Machine is properly provisioned according to the machine object, however attempts to SSH into it result in `connection timed out` errors. This error indicates that the SSH server is unreachable.
The most likely issues:
1. The Windows VM is unreachable on the network
2. SSH server is not running
3. The SSH server is blocked by Windows firewall

https://gcsweb-ci.apps.ci.l2s4.p1.openshiftapps.com/gcs/test-platform-results/pr-logs/pull/openshift_windows-machine-config-operator/2858/pull-ci-openshift-windows-machine-config-operator-release-4.18-azure-e2e-operator/1921970994168205312/artifacts/azure-e2e-operator/gather-extra/artifacts/pods/openshift-windows-machine-config-operator_windows-machine-config-operator-5d4c4958f6-hm7br_manager.log

      Version-Release number of selected component (if applicable):

      How reproducible:

      Not likely

      Steps to Reproduce:

          1. Spin up multiple 2019 Machines

      Actual results:

      Some Machines will be unable to be configured, and the VM is unable to be SSH'd into

      Expected results:

      Node is configured successfully, VM can be configured via SSH

      Additional info:

      Example job where this happens

https://prow.ci.openshift.org/view/gs/test-platform-results/pr-logs/pull/openshift_windows-machine-config-operator/2858/pull-ci-openshift-windows-machine-config-operator-release-4.18-azure-e2e-operator/1921970994168205312



In this test run the node logs pod is unable to connect via SSH as well.

https://gcsweb-ci.apps.ci.l2s4.p1.openshiftapps.com/gcs/test-platform-results/pr-logs/pull/openshift_windows-machine-config-operator/2858/pull-ci-openshift-windows-machine-config-operator-release-4.18-azure-e2e-operator/1921970994168205312/artifacts/azure-e2e-operator/windows-e2e-operator-test/artifacts/pods/job-name=print-logs-e2e-wm-m5czf-job-pbdwc/job-name=print-logs-e2e-wm-m5czf-job-pbdwc.log

              rh-ee-ssoto Sebastian Soto
              rh-ee-ssoto Sebastian Soto
              None
              None
              Aharon Rasouli Aharon Rasouli
              None
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

                Created:
                Updated:
                Resolved: