kubernetes-sigs/image-builder

Windows image builds failing with "UNREACHABLE"

mboersma opened this issue · 3 comments

mboersma commented

What steps did you take and what happened:

In CI runs and in our local pipelines, we have been seeing failures since about 2/26 building Windows Azure images:

/__w/1/s/images/capi/ansible/windows/node_windows.yml
    vhd-windows-2019:
    vhd-windows-2019: PLAY [all] *********************************************************************
    vhd-windows-2019:
    vhd-windows-2019: TASK [Gathering Facts] *********************************************************
    vhd-windows-2019: fatal: [default]: UNREACHABLE! => {"changed": false, "msg": "basic: HTTPSConnectionPool(host='104.210.147.200', port=5986): Max retries exceeded with url: /wsman (Caused by NewConnectionError('<urllib3.connection.VerifiedHTTPSConnection object at 0x7f463bf26eb0>: Failed to establish a new connection: [Errno 110] Connection timed out'))", "unreachable": true}
    vhd-windows-2019:
    vhd-windows-2019: PLAY RECAP *********************************************************************
    vhd-windows-2019: default                    : ok=0    changed=0    unreachable=1    failed=0    skipped=0    rescued=0    ignored=0
    vhd-windows-2019:
==> vhd-windows-2019: Provisioner failed with "Error executing Ansible: Non-zero exit status: exit status 4", retrying with 5 trie(s) left
==> vhd-windows-2019: Pausing 15s before the next provisioner...
==> vhd-windows-2019: Provisioning with Ansible...

It's intermittent, approximately 50% of the time.

What did you expect to happen:

Anything else you would like to add:

Environment:

Project (Image Builder for Cluster API):

Additional info for Image Builder for Cluster API related issues:

  • OS (e.g. from /etc/os-release, or cmd /c ver):
  • Packer Version:
  • Packer Provider:
  • Ansible Version:
  • Cluster-api version (if using):
  • Kubernetes version: (use kubectl version):

/kind bug

cc: @jsturtevant @marosset

k8s-triage-robot commented

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

mboersma commented

/close

This has not recurred since March AFAICT.

k8s-ci-robot commented

@mboersma: Closing this issue.

In response to this:

/close

This has not recurred since March AFAICT.

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.