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

Executing packer from Windows gives EOF error #5999

Closed kishore-vkrn closed 6 years ago

kishore-vkrn commented 6 years ago
rickard-von-essen commented 6 years ago

Can you fix the links. Thanks

kishore-vkrn commented 6 years ago

@rickard-von-essen links have been updated

mwhooker commented 6 years ago

Can you run the build again the the env var PACKER_LOG set?

kishore-vkrn commented 6 years ago

Find the below gist for the log

Log

kishore-vkrn commented 6 years ago

Any updates?

OwenGr commented 6 years ago

I'm receiving a similar error running packer in the hashicorp/packer docker image through Concourse targeting Azure, not AWS. I'm only building a Windows VM, not building from a Windows VM. Also, this pipeline functioned fine before the 1.2.4 update. It is still creating the Image in Azure, just failing during the resource cleanup.

I will get more logs. I'm not sure if this is the same issue or I should post a new one.

==> azure-arm: Deleting resource group ...
==> azure-arm:  -> ResourceGroupName : 'WTW-ESIE-CICD-DEV'
==> azure-arm: 
==> azure-arm: The resource group was not created by Packer, only deleting individual resources ...
==> azure-arm:  -> Microsoft.Compute/virtualMachines : 'BuildAgent'
==> azure-arm:  -> Microsoft.Network/networkInterfaces : 'pkrnirgjgq35zwn'
Build 'azure-arm' errored: unexpected EOF

==> Some builds didn't complete successfully and had errors:
--> azure-arm: unexpected EOF

==> Builds finished but no artifacts were created.
SwampDragons commented 6 years ago

@OwenGr if you're experiencing a regression since 1.2.4 it's probably not the same as this ticket, which has been open since well before that release. Can you open a new ticket with your issue and steps to reproduce?

@kishorramanan no updates yet, sorry. I haven't had a chance to look at your logs.

OwenGr commented 6 years ago

Confirmed it's a regression (at least, it works fine retargeting 1.2.3). I'll open another issue.

cloudbooster commented 6 years ago

@OwenGr let me know the new issue and would appreciate if you can provide your template details . Also can you confirm if its a consistent repro ? Typically unexpected EOF indicates failure down in SDK. I just pulled the latests source and I dont see the issue repro for me yet.

mwhooker commented 6 years ago

@kishorramanan Can you still reproduce on the latest packer? There's not much we can do about an older version

mariuszdotnet commented 6 years ago

Same issue as @OwenGr and same environment. Packer container in concourse with Azure.

Template is here: https://github.com/mariuszdotnet/image-rhel7/blob/master/template.json

Error:

==> azure-arm: The resource group was not created by Packer, only deleting individual resources ... ==> azure-arm: -> Microsoft.Compute/virtualMachines : 'pkrvmc2hx13bnnc' ==> azure-arm: -> Microsoft.Network/networkInterfaces : 'pkrnic2hx13bnnc' ==> azure-arm: -> Microsoft.Network/publicIPAddresses : 'pkripc2hx13bnnc' Build 'azure-arm' errored: unexpected EOF

==> Some builds didn't complete successfully and had errors: --> azure-arm: unexpected EOF

==> Builds finished but no artifacts were created.

SwampDragons commented 6 years ago

Closing since we never got acknowledgment of whether the Amazon issue is fixed in a recent packer. Looks like a fix has been merged for the commenters who say the Azure issue.

ghost commented 4 years ago

I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues.

If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.