Windows image build fails as ansible win_template module fails with FileNotFoundError

[outofmem0ry]

What steps did you take and what happened:
Followed the instructions to create a Windows image but the image building process failed with an error

fatal: [default]: FAILED! => {"changed": false, "msg": "FileNotFoundError: 
[Errno 2] No such file or directory: b'C:\\\\Program Files\\\\Cloudbase Solutions\\\\Cloudbase-Init\\\\conf\\\\cloudbase-init-unattend.conf'"}

Anything else you would like to add:
After some research on the issue looks like this was first fixed by #624 and later reverted by #657 removing ansible-base and eventually reverting the ansible version to 2.10.0 which still appears to have this problem. Temporarily worked around it by updating the version to 2.9.24.

I haven't tested with other 2.10.x versions but plan to do so.

• Packer Version: Packer v1.7.2

/kind bug

[perithompson]

/sig windows

[perithompson]

@jsturtevant I guess the ansible-galaxy update hasn't worked for everyone? I've had a couple of reports so I wonder if this is OS-dependent or something

[jsturtevant]

@outofmem0ry could you check that you have the correct windows package by running: ansible-galaxy collection list ansible.windows?

[mboersma]

I ran into the same problem, and after a lot of thrashing around found that updating ansible to 4.2.0 and installing ansible.windows explicitly seemed to work. YMMV of course, but here's the change I made in case it helps: https://github.com/deis/docker-go-dev/pull/307/files

[knabben]

If you have ansible installed in the path, it will bypass the ansible-windows installation, and unexpected process can happen. Maybe we need to check if ansible-windows exists after ansible check

[k8s-triage-robot]

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-triage-robot]

The Kubernetes project currently lacks enough active 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 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 rotten

[k8s-triage-robot]

The Kubernetes project currently lacks enough active 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:

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

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

/close

[k8s-ci-robot]

@k8s-triage-robot: Closing this issue.

In response to this:

The Kubernetes project currently lacks enough active 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:

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

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

/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.