search

hashicorp / packer

Packer is a tool for creating identical machine images for multiple platforms from a single source configuration.
http://www.packer.io
Other
15.11k stars 3.33k forks source link

Packer build fails with: `RPC client: Communicator ended with: 16001` during provisioning #7008

Open chogg82 opened 5 years ago

chogg82 commented 5 years ago

Packer AWS EBS build fails with: RPC client: Communicator ended with: 16001 during provisioning.

Build stripped back to that the provisioner does nothing but sleep for 10 minutes. This was because the same behaviour was seen when downloading large files (taking ~10 minutes) and I wanted to rule out any network related issues - this does seem to be time related.

Using latest AWS AMI for Windows 2016 Server Base (ami-0f5f78829606035fc).

User data enables WinRM and packer connects successfully.

Tried various timeout settings, including AWS_POLL_DELAY_SECONDS and AWS_MAX_ATTEMPTS but result remains the same.

Packer version: tried both latest and 1.2.5 Host platform: docker gist: here To recreate: simple powershell provisioner with sleep or long running command, aws ebs builder, using latest Windows Server 2016 Base AMI.

SwampDragons commented 5 years ago

Probably we need to figure out the winrm equivalent of a keepalive.

imonthercks commented 5 years ago

@chogg82, were you able to work around this somehow? Seeing the same thing with the AWS AMI for Windows 2016 Server Base, although only when running packer build from a linux container while it works fine from a windows machine.

garimakhulbe02 commented 1 year ago

We are started seeing this in azure-arm. were you able to workaround somehow? @chogg82