Puppet users - Oct 2011 - Cloud Provisioner: What works and what doesn't work?

Hi all, I''m very excited about using puppet cloud provisioner to spin
up new EC2 instances and have puppet auto-installed on them and then
get them to play their part by getting them classified using either
puppet master or puppet dashboard, so that each node will install all
the appropriate packages according to their roles.

However, I''m running into some troubles. Using puppet v2.7.3 with
cloud provisioner, I get some unexpected errors from the various
commands I try to run:

# puppet node bootstrap --image ami-XXXXXXXX --keypair puppet --login
root --keyfile /root/.ssh/puppet.pem --certname
mypuppetmaster.mydomain.com --type t1.micro

notice: Creating new instance ...
notice: Creating new instance ... Done
notice: Creating tags for instance ...
notice: Creating tags for instance ... Done
notice: Launching server i-12341234 ...
###############
notice: Server i-12341234 is now launched
notice: Server i-12341234 public dns name: ec2-XX-XX-XXX-
XXX.compute-1.amazonaws.com
notice: Waiting for SSH response ...
notice: Waiting for SSH response ... Done
notice: Installing Puppet ...
notice: Puppet is now installed on: ec2-XX-XX-XXX-
XXX.compute-1.amazonaws.com
notice: Signing certificate ...
err: Unknown options passed: image, keyfile, keypair, login, type
err: Try ''puppet help node bootstrap'' for usage

It complains that some required options are unknown: image, keyfile,
login, type
Clearly, I''m passing in those options, and it did spin up an instance,
and apparently installed puppet on it.
Should I ignore such errors, or is this an indication that something
is wrong in my setup?

Thanks!

-Eivind

-- 
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to
puppet-users+unsubscribe@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.

thanks for pointing out this issue. I have a feeling that this issue was
caused by some changes in how faces handles options between 2.7.2 and 2.7.3

The cloud provisioner definitely needs to be updated to work with the latest
version of Puppet.

could you try this out with 2.7.2rc3 and see if the issue still exists with
that version?

I am definitely not recommending this as a permanent fix, just trying to
collect some data.

thanks,

Dan

On Thu, Oct 6, 2011 at 12:03 PM, Eivind Hagen <eivind@sibblingz.com>
wrote:
> Hi all, I''m very excited about using puppet cloud provisioner to
spin
> up new EC2 instances and have puppet auto-installed on them and then
> get them to play their part by getting them classified using either
> puppet master or puppet dashboard, so that each node will install all
> the appropriate packages according to their roles.
>
> However, I''m running into some troubles. Using puppet v2.7.3 with
> cloud provisioner, I get some unexpected errors from the various
> commands I try to run:
>
> # puppet node bootstrap --image ami-XXXXXXXX --keypair puppet --login
> root --keyfile /root/.ssh/puppet.pem --certname
> mypuppetmaster.mydomain.com --type t1.micro
>
> notice: Creating new instance ...
> notice: Creating new instance ... Done
> notice: Creating tags for instance ...
> notice: Creating tags for instance ... Done
> notice: Launching server i-12341234 ...
> ###############
> notice: Server i-12341234 is now launched
> notice: Server i-12341234 public dns name: ec2-XX-XX-XXX-
> XXX.compute-1.amazonaws.com
> notice: Waiting for SSH response ...
> notice: Waiting for SSH response ... Done
> notice: Installing Puppet ...
> notice: Puppet is now installed on: ec2-XX-XX-XXX-
> XXX.compute-1.amazonaws.com
> notice: Signing certificate ...
> err: Unknown options passed: image, keyfile, keypair, login, type
> err: Try ''puppet help node bootstrap'' for usage
>
> It complains that some required options are unknown: image, keyfile,
> login, type
> Clearly, I''m passing in those options, and it did spin up an
instance,
> and apparently installed puppet on it.
> Should I ignore such errors, or is this an indication that something
> is wrong in my setup?
>
> Thanks!
>
> -Eivind
>
> --
> You received this message because you are subscribed to the Google Groups
> "Puppet Users" group.
> To post to this group, send email to puppet-users@googlegroups.com.
> To unsubscribe from this group, send email to
> puppet-users+unsubscribe@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/puppet-users?hl=en.
>
>
-- 
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to
puppet-users+unsubscribe@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.

This definitely was a bug:
    http://projects.puppetlabs.com/issues/10062

It has been resolved in master (the latest source) and will be fixed in the
next release.

On Sun, Oct 9, 2011 at 2:02 PM, Dan Bode <dan@puppetlabs.com> wrote:
> thanks for pointing out this issue. I have a feeling that this issue was
> caused by some changes in how faces handles options between 2.7.2 and 2.7.3
>
> The cloud provisioner definitely needs to be updated to work with the
> latest version of Puppet.
>
> could you try this out with 2.7.2rc3 and see if the issue still exists with
> that version?
>
> I am definitely not recommending this as a permanent fix, just trying to
> collect some data.
>
> thanks,
>
> Dan
>
>
> On Thu, Oct 6, 2011 at 12:03 PM, Eivind Hagen
<eivind@sibblingz.com>wrote:
>
>> Hi all, I''m very excited about using puppet cloud provisioner
to spin
>> up new EC2 instances and have puppet auto-installed on them and then
>> get them to play their part by getting them classified using either
>> puppet master or puppet dashboard, so that each node will install all
>> the appropriate packages according to their roles.
>>
>> However, I''m running into some troubles. Using puppet v2.7.3
with
>> cloud provisioner, I get some unexpected errors from the various
>> commands I try to run:
>>
>> # puppet node bootstrap --image ami-XXXXXXXX --keypair puppet --login
>> root --keyfile /root/.ssh/puppet.pem --certname
>> mypuppetmaster.mydomain.com --type t1.micro
>>
>> notice: Creating new instance ...
>> notice: Creating new instance ... Done
>> notice: Creating tags for instance ...
>> notice: Creating tags for instance ... Done
>> notice: Launching server i-12341234 ...
>> ###############
>> notice: Server i-12341234 is now launched
>> notice: Server i-12341234 public dns name: ec2-XX-XX-XXX-
>> XXX.compute-1.amazonaws.com
>> notice: Waiting for SSH response ...
>> notice: Waiting for SSH response ... Done
>> notice: Installing Puppet ...
>> notice: Puppet is now installed on: ec2-XX-XX-XXX-
>> XXX.compute-1.amazonaws.com
>> notice: Signing certificate ...
>> err: Unknown options passed: image, keyfile, keypair, login, type
>> err: Try ''puppet help node bootstrap'' for usage
>>
>> It complains that some required options are unknown: image, keyfile,
>> login, type
>> Clearly, I''m passing in those options, and it did spin up an
instance,
>> and apparently installed puppet on it.
>> Should I ignore such errors, or is this an indication that something
>> is wrong in my setup?
>>
>> Thanks!
>>
>> -Eivind
>>
>> --
>> You received this message because you are subscribed to the Google
Groups
>> "Puppet Users" group.
>> To post to this group, send email to puppet-users@googlegroups.com.
>> To unsubscribe from this group, send email to
>> puppet-users+unsubscribe@googlegroups.com.
>> For more options, visit this group at
>> http://groups.google.com/group/puppet-users?hl=en.
>>
>>
>
-- 
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to
puppet-users+unsubscribe@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.