similar to: puppet node_aws terminate and certificate cleanup

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

Hi, I am trying to bootstrap a new agent from my master node as below. puppet node_aws bootstrap \ --region us-east-1 \ --image ami-cc5af9a5 \ --login root \ --keyfile /root/.ssh/private.pem \ --install-script=puppet-enterprise \ --installer-payload=/usr/local/puppet/puppet-2.7.0.tar.gz \ --installer-answers=/usr/local/puppet/agent.txt \ --keyname icos-client \ --type t1.micro Node is created

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

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, My puppet master version:- #puppet --version 2.7.19 (Puppet Enterprise 2.7.0) While bootstrapping a new instance with my puppet master on Ec2,I am getting this error #puppet node_aws bootstrap --type t1.micro --image ami-00934969 --keyname ec2 --login root --keyfile ~/.ssh/ec2.pem --mode agent notice: Creating new instance ... notice: Creating new instance ... Done notice: Creating

Hi Guys, I''m unable to load the module cloud provisioner, when I try to run node_aws it gives me the below errors: Error: Could not autoload puppet/face/node_aws/list_keynames: no such file to load -- guid Error: Could not parse application options: Could not autoload puppet/face/node_aws/list_keynames: no such file to load -- guid And when I see the help list I can see the below

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 \

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")

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 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

How do I initiate a certificate request without going into non-daemon mode ? According to "Pro Puppet" book, so far the only way I know that can trigger a certficate request with puppet master is like this puppet agent --server=puppetmaster.test.com --no-daemonize --verbose but doing so will break my intention of automation I need to create a puppet client package. A control-C is

OS - RHEL5.7 Installation Source - epel-testing repo Puppet server version - 2.6.6 puppetd version - 2.6.6 I searched Google and none of the answers were a match for my set up... I can do ''puppetd --test'' from the client and things work as expected. When doing puppet kick hostname I get the following: Triggering hostname Host hostname failed: hostname not match with the server

Hello, I''m having trouble between the client and the master. Please help! *root@r3:~# puppet agent --test* Info: Caching certificate for r3.pb Info: Caching certificate_revocation_list for ca Warning: Unable to fetch my node definition, but the agent run will continue: Warning: SSL_connect returned=1 errno=0 state=SSLv3 read server certificate B: certificate verify failed:

Hi, My puppet master can''t bind ( ldap ) with my central server which has CACert assigned certificate. Are there any problem with Puppet with CACert? Or, how can I make that certificate trusted in my Puppet master? Any kind of help or hint appreciated. -- Best, Zico -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post

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

Hi all, I am trying to setup puppet master and puppetdb on same node using puppetdb module. When I try to run puppet agent -t, I see following erorr notice: Unable to connect to puppetdb server (ip-10-172-161-25.us-west-1.compute.internal:8081): SSL_connect returned=1 errno=0 state=SSLv3 read server certificate B: certificate verify failed notice: Failed to connect to puppetdb; sleeping 2

Hello, I am installing puppet and keep getting this error [Puppet could not request certificate: No route to host -connect(2)] My DNS is resloving and i can ping the master from the agent. I have added this line to the iptables [iptables -I INPUT -s 192.168.1.20 -m tcp -p tcp --dport 8140 -j ACCEPT], where the IP is my agent. I have also added my master ip to /etc/puppet/puppet.conf Why

Hello, I am trying to configure a new puppet server on Debian Squeeze, so the server version will be 2.6.2-4. I am trying to configure a client running Lenny, the puppet version is 0.25.4-2 I declare the new client with the command : #puppetd --server puppet.domain.tld --waitforcert 60 --test on the server : #puppetca --sign client.domain.tld When the client finish to execute the first

Hi all, Is there a more elegant way to regenerate the Puppet master certificate than what''s described in the CVE-2011-3872 toolkit? > If you can maintain a secondary shell session to the puppet master server, you can start a WEBrick master with puppet master --no-daemonize --verbose and stop it with ctrl-C. > If you prefer to only maintain one shell session, you can start a

Hi, I have puppet 3.0.1 installed with passenger and the clients are unables to request a certificate. I get a httpd error. 10.1.1.9 - - [11/Dec/2012:16:09:44 +0000] "GET /production/certificate/puppet-client2.tcl-oob.net? HTTP/1.1" 500 11298 "-" "-" When I run puppet master without passenger, I am able to request and sign certificates. I see this in http