SCP Error with Amazon Linux AMI 2018.03.0.20181129 x86_64 HVM ebs

[rob...@lunardelli.us]

The lastest Amazon Linux build is throwing an SCP error:

packer: 2018/12/06 14:40:38 [INFO] 32 bytes written for 'uploadData'

[INFO] 32 bytes written for 'uploadData'

packer: 2018/12/06 14:40:38 [DEBUG] Opening new ssh session

packer: 2018/12/06 14:40:38 [DEBUG] Starting remote scp process:  scp -vt /tmp

packer: 2018/12/06 14:40:38 [DEBUG] Started SCP session, beginning transfers...

packer: 2018/12/06 14:40:38 [DEBUG] Copying input data into temporary file so we can read the length

packer: 2018/12/06 14:40:38 [DEBUG] scp: Uploading script_2093.sh: perms=C0644 size=32

packer: 2018/12/06 14:40:38 [DEBUG] SCP session complete, closing stdin pipe.

packer: 2018/12/06 14:40:38 [DEBUG] Waiting for SSH session to complete.

packer: 2018/12/06 14:40:38 [DEBUG] non-zero exit status: 127

packer: 2018/12/06 14:40:38 [DEBUG] scp output:

packer: 2018/12/06 14:40:38 Retryable error: Error uploading script: SCP failed to start. This usually means that SCP is not

packer: properly installed on the remote system.

Ideas?

[rob...@lunardelli.us]

Packer version: 1.3.3

[Rickard von Essen]

Did you verify that scp is installed and working? 

--
This mailing list is governed under the HashiCorp Community Guidelines - https://www.hashicorp.com/community-guidelines.html. Behavior in violation of those guidelines may result in your removal from this mailing list.
 
GitHub Issues: https://github.com/mitchellh/packer/issues
IRC: #packer-tool on Freenode
---
You received this message because you are subscribed to the Google Groups "Packer" group.
To unsubscribe from this group and stop receiving emails from it, send an email to packer-tool...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/packer-tool/5f8b6111-1673-4590-89d2-002f3f7d179e%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[rob...@lunardelli.us]

I did. 

If I a EC2 instance manually and scp from my local host it works just fine. 

[Rickard von Essen]

A good way trying to debug this a bit is to use the null builder 1) against an instance that you manually launched and verified connectivity with. Turn on debug logging in sshd and see if there is any difference when packer fails and when your manual scp succeeds. 

Have you tried setting ssh_file_transfer_method to sftp? 2)

1) https://packer.io/docs/builders/null.html

2) https://packer.io/docs/templates/communicator.html#ssh_file_transfer_method

To view this discussion on the web visit https://groups.google.com/d/msgid/packer-tool/979692b8-198f-464b-bec3-bfc3d28f1a6a%40googlegroups.com.

[rob...@lunardelli.us]

sftp works pretty well.