similar to: Unable to use Cloud Provisioner

Hi everyone! having a slight problem with the installing the cloud provisioning module [code] http://docs.puppetlabs.com/guides/cloud_pack_getting_started.html [/code] everything worked until I wanted to actually try to fire it up: [code] >puppet node_aws list Error: Could not autoload puppet/face/node_aws/fingerprint: cannot load such file -- guid Error: Could not parse application

Hi ! I am currently testing puppet on CentOS 6 and I wish to test the cloud provisioner tool. The problem is the following : I can''t use fog because of ruby version issue. The system : CentOS 6.4 with Ruby 1.8.7 (last version for CentOS) What I did to get the problem : install puppet-server install module puppetlabs-cloud_provisioner Trying install Fog -v 0.7.2 (cloud service library

Hi all, When i try to boot an ec2 instance using: *puppet node_aws bootstrap --server myserverOnAWS.com --image ami-61ad0108 --keyname test-malcom --login ubuntu --type m1.small --keyfile test-malcom.pem -g puppets --verbose --debug --puppetagent-certname test* I get this error: *notice: Signing certificate ...* *debug: certificate_status supports formats: b64_zlib_yaml pson raw yaml; using

Hello, We''re trying to come up with a nice way to indicate when a Puppet module like cloud provisioner breaks a Puppet subcommand because of missing dependencies. When this happens in the current 3.0rc branch, all help for all subcommands is unavailable. This isn''t very helpful. We''re planning to simply mark the subcommands that have incomplete actions as

Any light someone can shed sure would be appreciated. I start with 1 cert -- the master''s, where I am running this: jblaine@ip-10-191-115-140:~$ sudo puppet cert list --all + "ip-10-191-115-140.ec2.internal" (74:8B:7B:EF:41:E6:F9:98:93:15:42:6A:4C:2F:28:CC) (alt names: "DNS:ip-10-191-115-140.ec2.internal", "DNS:puppet", "DNS:puppet.ec2.internal")

Was... Bash$ puppet node create This "create" action no longer exists. Has it been depreciated? Is the only way to create a node through puppetmaser now? Thanks, D -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To view this discussion on the web visit https://groups.google.com/d/msg/puppet-users/-/g3lJoO-j_u4J. To post

Hi, I am using the cloud provisioner to bootstrap some ec2 nodes, and these clients are signed using a randomly generated certname, which is put in /etc/puppet.conf at the bootstrap time (eg certname = d7bcd693-73fd-495f-0876-ff91ea11111e). But my puppet code repo also manages the puppet.conf file, so the file will be overwritten on the client at the first puppet run. Nevertheless, i should not

I have a very basic puppet install right now, running puppet master, with the dashboard and foreman on the same host, I have some legacy static nodes (nodes.pp) and now I am using puppet to provision nodes in EC2. I am running cloud provisioner .60rc1 and my question is what happens after a puppet node bootstrap? I''m running into some issues and maybe its just idiot user driving this

We are happy to announce the first public release candidate of our Puppet Cloud Provisioner. This release is available for download at our Module Forge: http://forge.puppetlabs.com/puppetlabs/cloud_provisioner<http://downloads.puppetlabs.com/dashboard/> Extensive documentation can be found at: http://docs.puppetlabs.com/guides/cloud_pack_getting_started.html Please report feedback via the

Hi, I am trying to install fog which is required for cloud provisioner. > gem install fog -v 0.7.2 I am getting the following error Building native extensions. This could take a while... ................ ERROR: Error installing fog: ERROR: Failed to build gem native extension. /usr/bin/ruby extconf.rb creating Makefile make

Hi, I have created an agent node from a master node using below command. puppet node_aws create --image ami-cc5af9a5 --keyname icos-client --type ti.micro Now as i am trying to install puppet on it using below command puppet node install \ --install-script=puppet- enterprise \ --installer-payload=/usr/local/puppet/puppet-2.7.0.tar.gz \ --installer-answers=/usr/local/puppet/agent.txt \

Hi! I''ve been playing with puppet node_aws on my ec2 instances and there is a problem which I don''t know how to solve it. The problem is: when i run puppet node_aws bootstrap in order to create and install puppet in new instance, I see at the end of logs: debug: Command: sudo puppet agent --configprint certname err: fingerprint f4:19:2a:53:b9:43:26:73:2e:b6:b7:9c:18:c3:db:aa

I thought I read somewhere in Puppet docs/wiki... that it is "recommended" to avoid spaces in file paths, or some similar verbiage, but now I cant find it. Does Puppet have any known issues with spaces in file paths? It would of course scare Windows admins away... So I hope I am wrong in thinking I read that. Thanks a lot, Mohamed. -- You received this message because you are

Hi, I am trying to install node_openstack module for puppet. But I see its dependency on puppetlabs-cloud_provisioner<https://forge.puppetlabs.com/puppetlabs-cloud_provisioner> (>= 1.0.2) Is this version available, if not is there any work around? regards, Haynes Davis ________________________________ This message is for the designated recipient only and may contain privileged,

Hi all, We''re getting close to release[1], so I''d appreciate it if people would start testing the current ''master'' branch with their repositories. I made quite a few internal changes, most of which shouldn''t even be noticed unless there are bugs, so just running a server and/or client under the current code would be a big help. I''m

Facter has the feature that it will turn any environment variable named FACTER_* into a fact. I can do this on the commandline no problem, but when I attempt this in puppet it seems to ignore that parts. Is anyone else seeing this? (Is this expected behavior?) I don''t see a ticket or a mail thread on it - though my searching powers have been weak the last couple of weeks... Thanks,

What is the right path for ruby gems on puppet master. Scenario: I have installed hiera couple of months back. So the gem was installed under /opt/puppet/lib/gems/1.8/gems/hiera-0.3.0 /opt/puppet/lib/gems/1.8/gems/hiera-puppet-0.3.0 Later when I updated to new version of hiera then it installed (via gem install) under /opt/puppet/lib/gems/1.8/gems/hiera-1.1.1

I''m still having some issues with cloud provisioner. I have a fresh install of provisioner, .60rc1, puppet 2.7.3, and dashboard 1.2.0. Everything has a very default install as described in the documentation. I was unable to get bootstrap to work, so I did things in a linear fashion (create, install, classify). Classify is failing and theres not really any good debug info, I just get

Does anyone know if puppet cleans up its certs when you terminate an instance via ''puppet node_aws terminate'' ? it doesn''t say in the docs. Thanks. -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To view this discussion on the web visit https://groups.google.com/d/msg/puppet-users/-/HJM1U9ic11gJ. To post

Having issues getting Puppet running under Passenger. From httpd error_log: [ pid=24647 thr=268010020 file=utils.rb:176 time=2011-10-04 11:45:10.892 ]: *** Exception LoadError in PhusionPassenger::Rack::ApplicationSpawner (no such file to load -- puppet/application/master) (process 24647, thread #<Thread: 0x0000001ff30448>): from