SSH keep-alive uses EC2 Internal IP

classic Classic list List threaded Threaded
3 messages Options
Reply | Threaded
Open this post in threaded view
|

SSH keep-alive uses EC2 Internal IP

J.P. Klousia
This was originally posted on github as an issue, but it certainly doesn't fall into that category yet, at least not for the project. I closed that out and hope that someone here can give me a few pointers on how to address this issue.

vagrant - 1.6.3
vagrant-aws - 0.5.0

I'm attempting to create and provision a CentOS 6.5 guest on AWS. I'm using a private AMI that has puppet installed. The machine appears to come up without trouble. All of the SSH communication appears to be using the correct ip address (initially). I'm able to successfully rsync all of the software from my local machine to the remote host and SSH to it directly from the command line etc. 

When puppet takes over to provision I see the following:

==> admin: Running Puppet with site.pp...
DEBUG ssh
: Re-using SSH connection.
 INFO ssh
: Execute: FACTER_environment='development' FACTER_vm_type='vagrant' puppet apply --verbose --modulepath '/tmp/vagrant-puppet-3/modules-0:/etc/puppet/modules' --manifestdir /tmp/vagrant-puppet-3/manifests --detailed-exitcodes /tmp/vagrant-puppet-3/manifests/site.pp (sudo=true)
DEBUG ssh
: stdout: Info: Loading facts in /tmp/vagrant-puppet-3/modules-0/orawls/lib/facter/orawls.rb
 INFO
interface: info: Info: Loading facts in /tmp/vagrant-puppet-3/modules-0/orawls/lib/facter/orawls.rb
 INFO
interface: info: ==> admin: Info: Loading facts in /tmp/vagrant-puppet-3/modules-0/orawls/lib/facter/orawls.rb
==> admin: Info: Loading facts in /tmp/vagrant-puppet-3/modules-0/orawls/lib/facter/orawls.rb
DEBUG ssh
: stdout:


DEBUG ssh
: stdout: Info: Loading facts in /etc/puppet/modules/orawls/lib/facter/orawls.rb
 INFO
interface: info: Info: Loading facts in /etc/puppet/modules/orawls/lib/facter/orawls.rb
 INFO
interface: info: ==> admin: Info: Loading facts in /etc/puppet/modules/orawls/lib/facter/orawls.rb
==> admin: Info: Loading facts in /etc/puppet/modules/orawls/lib/facter/orawls.rb
DEBUG ssh
: stdout:


DEBUG ssh
: Sending SSH keep-alive...
DEBUG ssh
: stderr: Error: Could not find default node or by name with 'ip-10-65-174-30.ec2.internal, ip-10-65-174-30.ec2, ip-10-65-174-30' on node ip-10-65-174-30.ec2.internal
 INFO
interface: info: Error: Could not find default node or by name with 'ip-10-65-174-30.ec2.internal, ip-10-65-174-30.ec2, ip-10-65-174-30' on node ip-10-65-174-30.ec2.internal
 INFO
interface: info: ==> admin: Error: Could not find default node or by name with 'ip-10-65-174-30.ec2.internal, ip-10-65-174-30.ec2, ip-10-65-174-30' on node ip-10-65-174-30.ec2.internal
==> admin: Error: Could not find default node or by name with 'ip-10-65-174-30.ec2.internal, ip-10-65-174-30.ec2, ip-10-65-174-30' on node ip-10-65-174-30.ec2.internal


The complete stack trace is below.

Stderr from the command:
Error: Could not find default node or by name with 'ip-10-65-174-30.ec2.internal, ip-10-65-174-30.ec2, ip-10-65-174-30' on node ip-10-65-174-30.ec2.internal
Error: Could not find default node or by name with 'ip-10-65-174-30.ec2.internal, ip-10-65-174-30.ec2, ip-10-65-174-30' on node ip-10-65-174-30.ec2.internal


ERROR vagrant
: /Applications/Vagrant/embedded/gems/gems/vagrant-1.6.3/plugins/communicators/ssh/communicator.rb:210:in `execute'
/Applications/Vagrant/embedded/gems/gems/vagrant-1.6.3/plugins/communicators/ssh/communicator.rb:220:in `
sudo'
/Applications/Vagrant/embedded/gems/gems/vagrant-1.6.3/plugins/provisioners/puppet/provisioner/puppet.rb:162:in `run_puppet_apply'

/Applications/Vagrant/embedded/gems/gems/vagrant-1.6.3/plugins/provisioners/puppet/provisioner/puppet.rb:82:in `provision'
/Applications/Vagrant/embedded/gems/gems/vagrant-1.6.3/lib/vagrant/action/builtin/provision.rb:129:in `
run_provisioner'
/Applications/Vagrant/embedded/gems/gems/vagrant-1.6.3/lib/vagrant/action/warden.rb:95:in `call'

/Applications/Vagrant/embedded/gems/gems/vagrant-1.6.3/lib/vagrant/action/warden.rb:95:in `block in finalize_action'
/Applications/Vagrant/embedded/gems/gems/vagrant-1.6.3/lib/vagrant/action/warden.rb:34:in `
call'
/Applications/Vagrant/embedded/gems/gems/vagrant-1.6.3/lib/vagrant/action/warden.rb:34:in `call'

/Applications/Vagrant/embedded/gems/gems/vagrant-1.6.3/lib/vagrant/action/builder.rb:116:in `call'
/Applications/Vagrant/embedded/gems/gems/vagrant-1.6.3/lib/vagrant/action/runner.rb:66:in `
block in run'
/Applications/Vagrant/embedded/gems/gems/vagrant-1.6.3/lib/vagrant/util/busy.rb:19:in `busy'

/Applications/Vagrant/embedded/gems/gems/vagrant-1.6.3/lib/vagrant/action/runner.rb:66:in `run'
/Applications/Vagrant/embedded/gems/gems/vagrant-1.6.3/lib/vagrant/environment.rb:346:in `
hook'
/Applications/Vagrant/embedded/gems/gems/vagrant-1.6.3/lib/vagrant/action/builtin/provision.rb:117:in `call'

/Applications/Vagrant/embedded/gems/gems/vagrant-1.6.3/lib/vagrant/action/builtin/provision.rb:117:in `block in call'
/Applications/Vagrant/embedded/gems/gems/vagrant-1.6.3/lib/vagrant/action/builtin/provision.rb:105:in `
each'
/Applications/Vagrant/embedded/gems/gems/vagrant-1.6.3/lib/vagrant/action/builtin/provision.rb:105:in `call'

/Applications/Vagrant/embedded/gems/gems/vagrant-1.6.3/lib/vagrant/action/warden.rb:34:in `call'
/Applications/Vagrant/embedded/gems/gems/vagrant-1.6.3/lib/vagrant/action/warden.rb:95:in `
block in finalize_action'
/Applications/Vagrant/embedded/gems/gems/vagrant-1.6.3/lib/vagrant/action/warden.rb:34:in `call'

/Applications/Vagrant/embedded/gems/gems/vagrant-1.6.3/lib/vagrant/action/warden.rb:34:in `call'
/Applications/Vagrant/embedded/gems/gems/vagrant-1.6.3/lib/vagrant/action/builder.rb:116:in `
call'
/Applications/Vagrant/embedded/gems/gems/vagrant-1.6.3/lib/vagrant/action/runner.rb:66:in `block in run'

/Applications/Vagrant/embedded/gems/gems/vagrant-1.6.3/lib/vagrant/util/busy.rb:19:in `busy'
/Applications/Vagrant/embedded/gems/gems/vagrant-1.6.3/lib/vagrant/action/runner.rb:66:in `
run'
/Applications/Vagrant/embedded/gems/gems/vagrant-1.6.3/lib/vagrant/action/builtin/call.rb:53:in `call'

/Applications/Vagrant/embedded/gems/gems/vagrant-1.6.3/lib/vagrant/action/warden.rb:34:in `call'
/Applications/Vagrant/embedded/gems/gems/vagrant-1.6.3/lib/vagrant/action/warden.rb:95:in `
block in finalize_action'
/Applications/Vagrant/embedded/gems/gems/vagrant-1.6.3/lib/vagrant/action/warden.rb:34:in `call'

/Applications/Vagrant/embedded/gems/gems/vagrant-1.6.3/lib/vagrant/action/warden.rb:34:in `call'
/Applications/Vagrant/embedded/gems/gems/vagrant-1.6.3/lib/vagrant/action/builder.rb:116:in `
call'
/Applications/Vagrant/embedded/gems/gems/vagrant-1.6.3/lib/vagrant/action/runner.rb:66:in `block in run'

/Applications/Vagrant/embedded/gems/gems/vagrant-1.6.3/lib/vagrant/util/busy.rb:19:in `busy'
/Applications/Vagrant/embedded/gems/gems/vagrant-1.6.3/lib/vagrant/action/runner.rb:66:in `
run'
/Applications/Vagrant/embedded/gems/gems/vagrant-1.6.3/lib/vagrant/action/builtin/call.rb:53:in `call'

/Applications/Vagrant/embedded/gems/gems/vagrant-1.6.3/lib/vagrant/action/warden.rb:34:in `call'
/Users/klousiaj/.vagrant.d/gems/gems/vagrant-aws-0.5.0/lib/vagrant-aws/action/connect_aws.rb:42:in `
call'
/Applications/Vagrant/embedded/gems/gems/vagrant-1.6.3/lib/vagrant/action/warden.rb:34:in `call'

/Applications/Vagrant/embedded/gems/gems/vagrant-1.6.3/lib/vagrant/action/builtin/config_validate.rb:25:in `call'
/Applications/Vagrant/embedded/gems/gems/vagrant-1.6.3/lib/vagrant/action/warden.rb:34:in `
call'
/Applications/Vagrant/embedded/gems/gems/vagrant-1.6.3/lib/vagrant/action/builtin/handle_box.rb:56:in `call'

/Applications/Vagrant/embedded/gems/gems/vagrant-1.6.3/lib/vagrant/action/builtin/handle_box_url.rb:9:in `call'
/Applications/Vagrant/embedded/gems/gems/vagrant-1.6.3/lib/vagrant/action/warden.rb:34:in `
call'
/Applications/Vagrant/embedded/gems/gems/vagrant-1.6.3/lib/vagrant/action/builder.rb:116:in `call'

/Applications/Vagrant/embedded/gems/gems/vagrant-1.6.3/lib/vagrant/action/runner.rb:66:in `block in run'
/Applications/Vagrant/embedded/gems/gems/vagrant-1.6.3/lib/vagrant/util/busy.rb:19:in `
busy'
/Applications/Vagrant/embedded/gems/gems/vagrant-1.6.3/lib/vagrant/action/runner.rb:66:in `run'

/Applications/Vagrant/embedded/gems/gems/vagrant-1.6.3/lib/vagrant/machine.rb:196:in `action_raw'
/Applications/Vagrant/embedded/gems/gems/vagrant-1.6.3/lib/vagrant/machine.rb:173:in `
block in action'
/Applications/Vagrant/embedded/gems/gems/vagrant-1.6.3/lib/vagrant/environment.rb:434:in `lock'

/Applications/Vagrant/embedded/gems/gems/vagrant-1.6.3/lib/vagrant/machine.rb:161:in `call'
/Applications/Vagrant/embedded/gems/gems/vagrant-1.6.3/lib/vagrant/machine.rb:161:in `
action'
/Applications/Vagrant/embedded/gems/gems/vagrant-1.6.3/lib/vagrant/batch_action.rb:82:in `block (2 levels) in run'

 INFO
interface: error: The following SSH command responded with a non-zero exit status.
Vagrant assumes that this means the command failed!


FACTER_environment
='development' FACTER_vm_type='vagrant' puppet apply --verbose --modulepath '/tmp/vagrant-puppet-3/modules-0:/etc/puppet/modules' --manifestdir /tmp/vagrant-puppet-3/manifests --detailed-exitcodes /tmp/vagrant-puppet-3/manifests/site.pp


Stdout from the command:


Info: Loading facts in /tmp/vagrant-puppet-3/modules-0/orawls/lib/facter/orawls.rb
Info: Loading facts in /etc/puppet/modules/orawls/lib/facter/orawls.rb

--
You received this message because you are subscribed to the Google Groups "Vagrant" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
For more options, visit https://groups.google.com/d/optout.
Reply | Threaded
Open this post in threaded view
|

Re: SSH keep-alive uses EC2 Internal IP

Terrance Shepherd
With out the puppet block does vagrant up and vagrant ssh work?


On Tue, Aug 19, 2014 at 12:21 PM, J.P. Klousia <[hidden email]> wrote:
This was originally posted on github as an issue, but it certainly doesn't fall into that category yet, at least not for the project. I closed that out and hope that someone here can give me a few pointers on how to address this issue.

vagrant - 1.6.3
vagrant-aws - 0.5.0

I'm attempting to create and provision a CentOS 6.5 guest on AWS. I'm using a private AMI that has puppet installed. The machine appears to come up without trouble. All of the SSH communication appears to be using the correct ip address (initially). I'm able to successfully rsync all of the software from my local machine to the remote host and SSH to it directly from the command line etc. 

When puppet takes over to provision I see the following:

==> admin: Running Puppet with site.pp...
DEBUG ssh
: Re-using SSH connection.
 INFO ssh
: Execute: FACTER_environment='development' FACTER_vm_type='vagrant' puppet apply --verbose --modulepath '/tmp/vagrant-puppet-3/modules-0:/etc/puppet/modules' --manifestdir /tmp/vagrant-puppet-3/manifests --detailed-exitcodes /tmp/vagrant-puppet-3/manifests/site.pp (sudo=true)
DEBUG ssh
: stdout: Info: Loading facts in /tmp/vagrant-puppet-3/modules-0/orawls/lib/facter/orawls.rb
 INFO
interface: info: Info: Loading facts in /tmp/vagrant-puppet-3/modules-0/orawls/lib/facter/orawls.rb
 INFO
interface: info: ==> admin: Info: Loading facts in /tmp/vagrant-puppet-3/modules-0/orawls/lib/facter/orawls.rb
==> admin: Info: Loading facts in /tmp/vagrant-puppet-3/modules-0/orawls/lib/facter/orawls.rb
DEBUG ssh
: stdout:


DEBUG ssh
: stdout: Info: Loading facts in /etc/puppet/modules/orawls/lib/facter/orawls.rb
 INFO
interface: info: Info: Loading facts in /etc/puppet/modules/orawls/lib/facter/orawls.rb
 INFO
interface: info: ==> admin: Info: Loading facts in /etc/puppet/modules/orawls/lib/facter/orawls.rb
==> admin: Info: Loading facts in /etc/puppet/modules/orawls/lib/facter/orawls.rb
DEBUG ssh
: stdout:


DEBUG ssh
: Sending SSH keep-alive...
DEBUG ssh
: stderr: Error: Could not find default node or by name with 'ip-10-65-174-30.ec2.internal, ip-10-65-174-30.ec2, ip-10-65-174-30' on node ip-10-65-174-30.ec2.internal
 INFO
interface: info: Error: Could not find default node or by name with 'ip-10-65-174-30.ec2.internal, ip-10-65-174-30.ec2, ip-10-65-174-30' on node ip-10-65-174-30.ec2.internal
 INFO
interface: info: ==> admin: Error: Could not find default node or by name with 'ip-10-65-174-30.ec2.internal, ip-10-65-174-30.ec2, ip-10-65-174-30' on node ip-10-65-174-30.ec2.internal
==> admin: Error: Could not find default node or by name with 'ip-10-65-174-30.ec2.internal, ip-10-65-174-30.ec2, ip-10-65-174-30' on node ip-10-65-174-30.ec2.internal


The complete stack trace is below.

Stderr from the command:
Error: Could not find default node or by name with 'ip-10-65-174-30.ec2.internal, ip-10-65-174-30.ec2, ip-10-65-174-30' on node ip-10-65-174-30.ec2.internal
Error: Could not find default node or by name with 'ip-10-65-174-30.ec2.internal, ip-10-65-174-30.ec2, ip-10-65-174-30' on node ip-10-65-174-30.ec2.internal


ERROR vagrant
: /Applications/Vagrant/embedded/gems/gems/vagrant-1.6.3/plugins/communicators/ssh/communicator.rb:210:in `execute'
/Applications/Vagrant/embedded/gems/gems/vagrant-1.6.3/plugins/communicators/ssh/communicator.rb:220:in `
sudo'
/Applications/Vagrant/embedded/gems/gems/vagrant-1.6.3/plugins/provisioners/puppet/provisioner/puppet.rb:162:in `run_puppet_apply'

/Applications/Vagrant/embedded/gems/gems/vagrant-1.6.3/plugins/provisioners/puppet/provisioner/puppet.rb:82:in `provision'
/Applications/Vagrant/embedded/gems/gems/vagrant-1.6.3/lib/vagrant/action/builtin/provision.rb:129:in `
run_provisioner'
/Applications/Vagrant/embedded/gems/gems/vagrant-1.6.3/lib/vagrant/action/warden.rb:95:in `call'

/Applications/Vagrant/embedded/gems/gems/vagrant-1.6.3/lib/vagrant/action/warden.rb:95:in `block in finalize_action'
/Applications/Vagrant/embedded/gems/gems/vagrant-1.6.3/lib/vagrant/action/warden.rb:34:in `
call'
/Applications/Vagrant/embedded/gems/gems/vagrant-1.6.3/lib/vagrant/action/warden.rb:34:in `call'

/Applications/Vagrant/embedded/gems/gems/vagrant-1.6.3/lib/vagrant/action/builder.rb:116:in `call'
/Applications/Vagrant/embedded/gems/gems/vagrant-1.6.3/lib/vagrant/action/runner.rb:66:in `
block in run'
/Applications/Vagrant/embedded/gems/gems/vagrant-1.6.3/lib/vagrant/util/busy.rb:19:in `busy'

/Applications/Vagrant/embedded/gems/gems/vagrant-1.6.3/lib/vagrant/action/runner.rb:66:in `run'
/Applications/Vagrant/embedded/gems/gems/vagrant-1.6.3/lib/vagrant/environment.rb:346:in `
hook'
/Applications/Vagrant/embedded/gems/gems/vagrant-1.6.3/lib/vagrant/action/builtin/provision.rb:117:in `call'

/Applications/Vagrant/embedded/gems/gems/vagrant-1.6.3/lib/vagrant/action/builtin/provision.rb:117:in `block in call'
/Applications/Vagrant/embedded/gems/gems/vagrant-1.6.3/lib/vagrant/action/builtin/provision.rb:105:in `
each'
/Applications/Vagrant/embedded/gems/gems/vagrant-1.6.3/lib/vagrant/action/builtin/provision.rb:105:in `call'

/Applications/Vagrant/embedded/gems/gems/vagrant-1.6.3/lib/vagrant/action/warden.rb:34:in `call'
/Applications/Vagrant/embedded/gems/gems/vagrant-1.6.3/lib/vagrant/action/warden.rb:95:in `
block in finalize_action'
/Applications/Vagrant/embedded/gems/gems/vagrant-1.6.3/lib/vagrant/action/warden.rb:34:in `call'

/Applications/Vagrant/embedded/gems/gems/vagrant-1.6.3/lib/vagrant/action/warden.rb:34:in `call'
/Applications/Vagrant/embedded/gems/gems/vagrant-1.6.3/lib/vagrant/action/builder.rb:116:in `
call'
/Applications/Vagrant/embedded/gems/gems/vagrant-1.6.3/lib/vagrant/action/runner.rb:66:in `block in run'

/Applications/Vagrant/embedded/gems/gems/vagrant-1.6.3/lib/vagrant/util/busy.rb:19:in `busy'
/Applications/Vagrant/embedded/gems/gems/vagrant-1.6.3/lib/vagrant/action/runner.rb:66:in `
run'
/Applications/Vagrant/embedded/gems/gems/vagrant-1.6.3/lib/vagrant/action/builtin/call.rb:53:in `call'

/Applications/Vagrant/embedded/gems/gems/vagrant-1.6.3/lib/vagrant/action/warden.rb:34:in `call'
/Applications/Vagrant/embedded/gems/gems/vagrant-1.6.3/lib/vagrant/action/warden.rb:95:in `
block in finalize_action'
/Applications/Vagrant/embedded/gems/gems/vagrant-1.6.3/lib/vagrant/action/warden.rb:34:in `call'

/Applications/Vagrant/embedded/gems/gems/vagrant-1.6.3/lib/vagrant/action/warden.rb:34:in `call'
/Applications/Vagrant/embedded/gems/gems/vagrant-1.6.3/lib/vagrant/action/builder.rb:116:in `
call'
/Applications/Vagrant/embedded/gems/gems/vagrant-1.6.3/lib/vagrant/action/runner.rb:66:in `block in run'

/Applications/Vagrant/embedded/gems/gems/vagrant-1.6.3/lib/vagrant/util/busy.rb:19:in `busy'
/Applications/Vagrant/embedded/gems/gems/vagrant-1.6.3/lib/vagrant/action/runner.rb:66:in `
run'
/Applications/Vagrant/embedded/gems/gems/vagrant-1.6.3/lib/vagrant/action/builtin/call.rb:53:in `call'

/Applications/Vagrant/embedded/gems/gems/vagrant-1.6.3/lib/vagrant/action/warden.rb:34:in `call'
/Users/klousiaj/.vagrant.d/gems/gems/vagrant-aws-0.5.0/lib/vagrant-aws/action/connect_aws.rb:42:in `
call'
/Applications/Vagrant/embedded/gems/gems/vagrant-1.6.3/lib/vagrant/action/warden.rb:34:in `call'

/Applications/Vagrant/embedded/gems/gems/vagrant-1.6.3/lib/vagrant/action/builtin/config_validate.rb:25:in `call'
/Applications/Vagrant/embedded/gems/gems/vagrant-1.6.3/lib/vagrant/action/warden.rb:34:in `
call'
/Applications/Vagrant/embedded/gems/gems/vagrant-1.6.3/lib/vagrant/action/builtin/handle_box.rb:56:in `call'

/Applications/Vagrant/embedded/gems/gems/vagrant-1.6.3/lib/vagrant/action/builtin/handle_box_url.rb:9:in `call'
/Applications/Vagrant/embedded/gems/gems/vagrant-1.6.3/lib/vagrant/action/warden.rb:34:in `
call'
/Applications/Vagrant/embedded/gems/gems/vagrant-1.6.3/lib/vagrant/action/builder.rb:116:in `call'

/Applications/Vagrant/embedded/gems/gems/vagrant-1.6.3/lib/vagrant/action/runner.rb:66:in `block in run'
/Applications/Vagrant/embedded/gems/gems/vagrant-1.6.3/lib/vagrant/util/busy.rb:19:in `
busy'
/Applications/Vagrant/embedded/gems/gems/vagrant-1.6.3/lib/vagrant/action/runner.rb:66:in `run'

/Applications/Vagrant/embedded/gems/gems/vagrant-1.6.3/lib/vagrant/machine.rb:196:in `action_raw'
/Applications/Vagrant/embedded/gems/gems/vagrant-1.6.3/lib/vagrant/machine.rb:173:in `
block in action'
/Applications/Vagrant/embedded/gems/gems/vagrant-1.6.3/lib/vagrant/environment.rb:434:in `lock'

/Applications/Vagrant/embedded/gems/gems/vagrant-1.6.3/lib/vagrant/machine.rb:161:in `call'
/Applications/Vagrant/embedded/gems/gems/vagrant-1.6.3/lib/vagrant/machine.rb:161:in `
action'
/Applications/Vagrant/embedded/gems/gems/vagrant-1.6.3/lib/vagrant/batch_action.rb:82:in `block (2 levels) in run'

 INFO
interface: error: The following SSH command responded with a non-zero exit status.
Vagrant assumes that this means the command failed!


FACTER_environment
='development' FACTER_vm_type='vagrant' puppet apply --verbose --modulepath '/tmp/vagrant-puppet-3/modules-0:/etc/puppet/modules' --manifestdir /tmp/vagrant-puppet-3/manifests --detailed-exitcodes /tmp/vagrant-puppet-3/manifests/site.pp


Stdout from the command:


Info: Loading facts in /tmp/vagrant-puppet-3/modules-0/orawls/lib/facter/orawls.rb
Info: Loading facts in /etc/puppet/modules/orawls/lib/facter/orawls.rb

--
You received this message because you are subscribed to the Google Groups "Vagrant" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
For more options, visit https://groups.google.com/d/optout.

--
You received this message because you are subscribed to the Google Groups "Vagrant" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
For more options, visit https://groups.google.com/d/optout.
Reply | Threaded
Open this post in threaded view
|

Re: SSH keep-alive uses EC2 Internal IP

J.P. Klousia
In reply to this post by J.P. Klousia
Yes, without the puppet block everything looks just fine.

On Tuesday, August 19, 2014 12:21:00 PM UTC-4, J.P. Klousia wrote:
This was originally posted on github as an issue, but it certainly doesn't fall into that category yet, at least not for the project. I closed that out and hope that someone here can give me a few pointers on how to address this issue.

vagrant - 1.6.3
vagrant-aws - 0.5.0

I'm attempting to create and provision a CentOS 6.5 guest on AWS. I'm using a private AMI that has puppet installed. The machine appears to come up without trouble. All of the SSH communication appears to be using the correct ip address (initially). I'm able to successfully rsync all of the software from my local machine to the remote host and SSH to it directly from the command line etc. 

When puppet takes over to provision I see the following:

==> admin: Running Puppet with site.pp...
DEBUG ssh
: Re-using SSH connection.
 INFO ssh
: Execute: FACTER_environment='development' FACTER_vm_type='vagrant' puppet apply --verbose --modulepath '/tmp/vagrant-puppet-3/modules-0:/etc/puppet/modules' --manifestdir /tmp/vagrant-puppet-3/manifests --detailed-exitcodes /tmp/vagrant-puppet-3/manifests/site.pp (sudo=true)
DEBUG ssh
: stdout: Info: Loading facts in /tmp/vagrant-puppet-3/modules-0/orawls/lib/facter/orawls.rb
 INFO
interface: info: Info: Loading facts in /tmp/vagrant-puppet-3/modules-0/orawls/lib/facter/orawls.rb
 INFO
interface: info: ==> admin: Info: Loading facts in /tmp/vagrant-puppet-3/modules-0/orawls/lib/facter/orawls.rb
==> admin: Info: Loading facts in /tmp/vagrant-puppet-3/modules-0/orawls/lib/facter/orawls.rb
DEBUG ssh
: stdout:


DEBUG ssh
: stdout: Info: Loading facts in /etc/puppet/modules/orawls/lib/facter/orawls.rb
 INFO
interface: info: Info: Loading facts in /etc/puppet/modules/orawls/lib/facter/orawls.rb
 INFO
interface: info: ==> admin: Info: Loading facts in /etc/puppet/modules/orawls/lib/facter/orawls.rb
==> admin: Info: Loading facts in /etc/puppet/modules/orawls/lib/facter/orawls.rb
DEBUG ssh
: stdout:


DEBUG ssh
: Sending SSH keep-alive...
DEBUG ssh
: stderr: Error: Could not find default node or by name with 'ip-10-65-174-30.ec2.internal, ip-10-65-174-30.ec2, ip-10-65-174-30' on node ip-10-65-174-30.ec2.internal
 INFO
interface: info: Error: Could not find default node or by name with 'ip-10-65-174-30.ec2.internal, ip-10-65-174-30.ec2, ip-10-65-174-30' on node ip-10-65-174-30.ec2.internal
 INFO
interface: info: ==> admin: Error: Could not find default node or by name with 'ip-10-65-174-30.ec2.internal, ip-10-65-174-30.ec2, ip-10-65-174-30' on node ip-10-65-174-30.ec2.internal
==> admin: Error: Could not find default node or by name with 'ip-10-65-174-30.ec2.internal, ip-10-65-174-30.ec2, ip-10-65-174-30' on node ip-10-65-174-30.ec2.internal


The complete stack trace is below.

Stderr from the command:
Error: Could not find default node or by name with 'ip-10-65-174-30.ec2.internal, ip-10-65-174-30.ec2, ip-10-65-174-30' on node ip-10-65-174-30.ec2.internal
Error: Could not find default node or by name with 'ip-10-65-174-30.ec2.internal, ip-10-65-174-30.ec2, ip-10-65-174-30' on node ip-10-65-174-30.ec2.internal


ERROR vagrant
: /Applications/Vagrant/embedded/gems/gems/vagrant-1.6.3/plugins/communicators/ssh/communicator.rb:210:in `execute'
/Applications/Vagrant/embedded/gems/gems/vagrant-1.6.3/plugins/communicators/ssh/communicator.rb:220:in `
sudo'
/Applications/Vagrant/embedded/gems/gems/vagrant-1.6.3/plugins/provisioners/puppet/provisioner/puppet.rb:162:in `run_puppet_apply'

/Applications/Vagrant/embedded/gems/gems/vagrant-1.6.3/plugins/provisioners/puppet<span style="color: #
...

--
You received this message because you are subscribed to the Google Groups "Vagrant" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
For more options, visit https://groups.google.com/d/optout.