On Thu, Oct 6, 2011 at 1:41 PM, Joshua Vaughn-Uding <unix.magic...@gmail.com
> wrote:
> 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 this:
>
> root@ip-10-36-11-244:/etc/puppet/manifests# puppet node install
> ec2-50-19-149-210.compute-1.amazonaws.com --login root --keyfile /
> root/.ssh/puppet.pem --install-script gems --puppet-version 2.7.5
> notice: Waiting for SSH response ...
> notice: Waiting for SSH response ... Done
> notice: Installing Puppet ...
> info: access[^/catalog/([^/]+)$]: allowing 'method' find
> info: access[^/catalog/([^/]+)$]: allowing $1 access
> info: access[^/node/([^/]+)$]: allowing 'method' find
> info: access[^/node/([^/]+)$]: allowing $1 access
> info: access[/certificate_revocation_list/ca]: allowing 'method' find
> info: access[/certificate_revocation_list/ca]: allowing * access
> info: access[/report]: allowing 'method' save
> info: access[/report]: allowing * access
> info: access[/file]: allowing * access
> info: access[/certificate/ca]: adding authentication no
> info: access[/certificate/ca]: allowing 'method' find
> info: access[/certificate/ca]: allowing * access
> info: access[/certificate/]: adding authentication no
> info: access[/certificate/]: allowing 'method' find
> info: access[/certificate/]: allowing * access
> info: access[/certificate_request]: adding authentication no
> info: access[/certificate_request]: allowing 'method' find
> info: access[/certificate_request]: allowing 'method' save
> info: access[/certificate_request]: allowing * access
> info: access[/]: adding authentication any
> info: access[/certificate_status]: allowing 'method' save
> info: access[/certificate_status]: adding authentication yes
> info: access[/certificate_status]: allowing * access
> info: Inserting default '/status'(auth) ACL because none were found in
> '/etc/puppet/auth.conf'
> info: Inserting default '/resource'(auth) ACL because none were found
> in '/etc/puppet/auth.conf'
> info: Could not find certificate for '2c96865c-deb0-a646-2d94-
> c4287f72650f'
> info: Could not find certificate_request for '2c96865c-deb0-a646-2d94-
> c4287f72650f'
> notice: 2c96865c-deb0-a646-2d94-c4287f72650f has a waiting certificate
> request
> notice: Signed certificate request for 2c96865c-deb0-a646-2d94-
> c4287f72650f
> notice: Removing file Puppet::SSL::CertificateRequest 2c96865c-deb0-
> a646-2d94-c4287f72650f at '/etc/puppet/ssl/ca/requests/2c96865c-deb0-
> a646-2d94-c4287f72650f.pem'
> 2c96865c-deb0-a646-2d94-c4287f72650f
> root@ip-10-36-11-244:/etc/puppet/manifests# puppet node classify
> ec2-50-19-149-210.compute-1.amazonaws.com --mode agent --node-
> group=puppet-agentsnotice: Registering node ...
> err: Connection reset by peer
> err: Try 'puppet help node classify' for usage
>
It looks like that you have not set the options that let the classify action
know how to connect to the dashboard.
You need to set:
report_server: hostname of dashboard
report_port: dashboard port (3000)
In the version that you are using, the node classify action does not have
the best logging.
I would recommend trying out the version in master (if you don't mind
running from source) The latest version has some improved logging for the
classification action.
I would also recommend running the classify action with --verbose enabled
> nothing shows up in dashboard, a check of the syslog on the client
> reveals:
>
> Oct 6 19:50:19 domU-12-31-39-0C-10-C7 puppet-agent[1279]: (/File[/var/
> lib/puppet/lib/puppet/face/node/terminate.rb]/ensure) defined content
> as '{md5}58a4dadeb4194a3cb285f1d2ec582bd2'
> Oct 6 19:50:19 domU-12-31-39-0C-10-C7 puppet-agent[1279]: Loading
> downloaded plugin /var/lib/puppet/lib/puppet/cloudpack.rb
> Oct 6 19:50:19 domU-12-31-39-0C-10-C7 puppet-agent[1279]: Could not
> load downloaded file /var/lib/puppet/lib/puppet/cloudpack.rb: no such
> file to load -- guid
> Oct 6 19:50:19 domU-12-31-39-0C-10-C7 puppet-agent[1279]: Loading
> downloaded plugin /var/lib/puppet/lib/puppet/face/node/classify.rb
> Oct 6 19:50:19 domU-12-31-39-0C-10-C7 puppet-agent[1279]: Could not
> load downloaded file /var/lib/puppet/lib/puppet/face/node/classify.rb:
> no such file to load -- guid
> Oct 6 19:50:19 domU-12-31-39-0C-10-C7 puppet-agent[1279]: Loading
> downloaded plugin /var/lib/puppet/lib/puppet/face/node/terminate.rb
> Oct 6 19:50:19 domU-12-31-39-0C-10-C7 puppet-agent[1279]: Could not
> load downloaded file /var/lib/puppet/lib/puppet/face/node/
> terminate.rb: no such file to load -- guid
> Oct 6 19:50:19 domU-12-31-39-0C-10-C7 puppet-agent[1279]: Loading
> downloaded plugin /var/lib/puppet/lib/puppet/face/node/init.rb
> Oct 6 19:50:19 domU-12-31-39-0C-10-C7 puppet-agent[1279]: Could not
> load downloaded file /var/lib/puppet/lib/puppet/face/node/init.rb: no
> such file to load -- guid
> Oct 6 19:50:19 domU-12-31-39-0C-10-C7 puppet-agent[1279]: Loading
> downloaded plugin /var/lib/puppet/lib/puppet/cloudpack/scripts/puppet-
> enterprise.erb
> Oct 6 19:50:19 domU-12-31-39-0C-10-C7 puppet-agent[1279]: Could not
> load downloaded file /var/lib/puppet/lib/puppet/cloudpack/scripts/
> puppet-enterprise.erb: /var/lib/puppet/lib/puppet/cloudpack/scripts/
> puppet-enterprise.erb:6: unterminated string meets end of file
> Oct 6 19:50:19 domU-12-31-39-0C-10-C7 puppet-agent[1279]: Loading
> downloaded plugin /var/lib/puppet/lib/puppet/face/node/fingerprint.rb
> Oct 6 19:50:19 domU-12-31-39-0C-10-C7 puppet-agent[1279]: Could not
> load downloaded file /var/lib/puppet/lib/puppet/face/node/
> fingerprint.rb: no such file to load -- guid
> Oct 6 19:50:19 domU-12-31-39-0C-10-C7 puppet-agent[1279]: Loading
> downloaded plugin /var/lib/puppet/lib/puppet/face/node/create.rb
> Oct 6 19:50:19 domU-12-31-39-0C-10-C7 puppet-agent[1279]: Could not
> load downloaded file /var/lib/puppet/lib/puppet/face/node/create.rb:
> no such file to load -- guid
> Oct 6 19:50:19 domU-12-31-39-0C-10-C7 puppet-agent[1279]: Loading
> downloaded plugin /var/lib/puppet/lib/puppet/cloudpack/installer.rb
> Oct 6 19:50:19 domU-12-31-39-0C-10-C7 puppet-agent[1279]: Could not
> load downloaded file /var/lib/puppet/lib/puppet/cloudpack/
> installer.rb: no such file to load -- guid
> Oct 6 19:50:19 domU-12-31-39-0C-10-C7 puppet-agent[1279]: Loading
> downloaded plugin /var/lib/puppet/lib/puppet/face/node/bootstrap.rb
> Oct 6 19:50:19 domU-12-31-39-0C-10-C7 puppet-agent[1279]: Could not
> load downloaded file /var/lib/puppet/lib/puppet/face/node/
> bootstrap.rb: no such file to load -- guid
> Oct 6 19:50:19 domU-12-31-39-0C-10-C7 puppet-agent[1279]: Loading
> downloaded plugin /var/lib/puppet/lib/puppet/face/node/list.rb
> Oct 6 19:50:19 domU-12-31-39-0C-10-C7 puppet-agent[1279]: Could not
> load downloaded file /var/lib/puppet/lib/puppet/face/node/list.rb: no
> such file to load -- guid
> Oct 6 19:50:19 domU-12-31-39-0C-10-C7 puppet-agent[1279]: Loading
> downloaded plugin /var/lib/puppet/lib/puppet/cloudpack/scripts/puppet-
> enterprise-s3.erb
> Oct 6 19:50:19 domU-12-31-39-0C-10-C7 puppet-agent[1279]: Could not
> load downloaded file /var/lib/puppet/lib/puppet/cloudpack/scripts/
> puppet-enterprise-s3.erb: /var/lib/puppet/lib/puppet/cloudpack/scripts/
> puppet-enterprise-s3.erb:18: syntax error, unexpected tSYMBEG,
> expecting kDO or '{' or '('#012wget --progress=dot:mega "https://
> puppetlabs.s3.am...#012 ^
> Oct 6 19:50:19 domU-12-31-39-0C-10-C7 puppet-agent[1279]: Loading
> downloaded plugin /var/lib/puppet/lib/puppet/cloudpack/scripts/
> gems.erb
> Oct 6 19:50:19 domU-12-31-39-0C-10-C7 puppet-agent[1279]: Could not
> load downloaded file /var/lib/puppet/lib/puppet/cloudpack/scripts/
> gems.erb: /var/lib/puppet/lib/puppet/cloudpack/scripts/gems.erb:8:
> syntax error, unexpected tREGEXP_BEG, expecting kDO or '{' or
> '('#012if [ -f /etc/redhat-release ]; then#012 ^#012/var/lib/
> puppet/lib/puppet/cloudpack/scripts/gems.erb:8: unknown regexp options
> - rdhat#012/var/lib/puppet/lib/puppet/cloudpack/scripts/gems.erb:8:
> syntax error, unexpected ']', expecting $end#012if [ -f /etc/redhat-
> release ]; then#012 ^
> Oct 6 19:50:19 domU-12-31-39-0C-10-C7 puppet-agent[1279]: Loading
> downloaded plugin /var/lib/puppet/lib/puppet/face/node/install.rb
> Oct 6 19:50:19 domU-12-31-39-0C-10-C7 puppet-agent[1279]: Could not
> load downloaded file /var/lib/puppet/lib/puppet/face/node/install.rb:
> no such file to load -- guid
> Oct 6 19:50:19 domU-12-31-39-0C-10-C7 puppet-agent[1279]: Loading
> downloaded plugin /var/lib/puppet/lib/puppet/cloudpack/scripts/
> master_source_dev.erb
> Oct 6 19:50:19 domU-12-31-39-0C-10-C7 puppet-agent[1279]: Could not
> load downloaded file /var/lib/puppet/lib/puppet/cloudpack/scripts/
> master_source_dev.erb: /var/lib/puppet/lib/puppet/cloudpack/scripts/
> master_source_dev.erb:10: syntax error, unexpected tREGEXP_BEG,
> expecting kDO or '{' or '('#012if [ -f /etc/redhat-release ];
> then#012 ^#012/var/lib/puppet/lib/puppet/cloudpack/scripts/
> master_source_dev.erb:10: unknown regexp options - rdhat#012/var/lib/
> puppet/lib/puppet/cloudpack/scripts/master_source_dev.erb:10: syntax
> error, unexpected ']', expecting $end#012if [ -f /etc/redhat-
> release ]; then#012
The above logs seem to indicate that cloud provisioner does not work well as
a puppet module (and can probably be disregarded for now). It looks like
plugin sync is failing when the agent runs.
> ^
> Oct 6 19:50:27 domU-12-31-39-0C-10-C7 puppet-agent[1279]: Could not
> retrieve catalog from remote server: Error 400 on SERVER: Could not
> find node 'c86ce7c5-f0b7-64f3-2862-6c0346319d84'; cannot compile
> Oct 6 19:50:27 domU-12-31-39-0C-10-C7 puppet-agent[1279]: Not using
> cache on failed catalog
> Oct 6 19:50:27 domU-12-31-39-0C-10-C7 puppet-agent[1279]: Could not
> retrieve catalog; skipping run
> Oct 6 20:21:56 domU-12-31-39-0C-10-C7 puppet-agent[2157]: Creating a
> new SSL key for 9c20a874-bf3f-06c9-ad5a-c1593e21ec5b
> Oct 6 20:21:56 domU-12-31-39-0C-10-C
the above logs are probably just a side effect of the classify action
failing
> puppet-agent[2157]: Could not
> request certificate: Error 400 on SERVER: Invalid pattern {certname}
> at line 104 of /etc/puppet/auth.conf
>
I am not sure what this indicates, could you share the lines around 104 in
auth.conf?
> Oct 6 20:27:28 domU-12-31-39-0C-10-C7 puppet-agent[2500]: Creating a
> new SSL key for 2c96865c-deb0-a646-2d94-c4287f72650f
> Oct 6 20:27:30 domU-12-31-39-0C-10-C7 puppet-agent[2500]: Caching
> certificate for ca
> Oct 6 20:27:31 domU-12-31-39-0C-10-C7 puppet-agent[2500]: Creating a
> new SSL certificate request for 2c96865c-deb0-a646-2d94-c4287f72650f
> Oct 6 20:27:31 domU-12-31-39-0C-10-C7 puppet-agent[2500]: Certificate
> Request fingerprint (md5): 86:43:B5:B8:81:8E:4E:40:F1:46:FF:71:8D:
> 12:D7:EB
> Oct 6 20:27:31 domU-12-31-39-0C-10-C7 puppet-agent[2500]: Caching
> certificate for 2c96865c-deb0-a646-2d94-c4287f72650f
> Oct 6 20:27:31 domU-12-31-39-0C-10-C7 puppet-agent[2500]: Retrieving
> plugin
> Oct 6 20:27:31 domU-12-31-39-0C-10-C7 puppet-agent[2500]: (/File[/var/
> lib/puppet/lib]) Failed to generate additional resources using
> 'eval_generate: SSL_connect returned=1 errno=0 state=SSLv3 read server
> certificate B: certificate verify failed. This is often because the
> time is out of sync on the server or client
> Oct 6 20:27:31 domU-12-31-39-0C-10-C7 puppet-agent[2500]: (/File[/var/
> lib/puppet/lib]) Could not evaluate: SSL_connect returned=1 errno=0
> state=SSLv3 read server certificate B: certificate verify failed.
> This is often because the time is out of sync on the server or client
> Could not retrieve file metadata for puppet://puppet/plugins:
> SSL_connect returned=1 errno=0 state=SSLv3 read server certificate B:
> certificate verify failed. This is often because the time is out of
> sync on the server or client
> Oct 6 20:27:33 domU-12-31-39-0C-10-C7 puppet-agent[2500]: Could not
> retrieve catalog from remote server: SSL_connect returned=1 errno=0
> state=SSLv3 read server certificate B: certificate verify failed.
> This is often because the time is out of sync on the server or client
> Oct 6 20:27:33 domU-12-31-39-0C-10-C7 puppet-agent[2500]: Not using
> cache on failed catalog
> Oct 6 20:27:33 domU-12-31-39-0C-10-C7 puppet-agent[2500]: Could not
> retrieve catalog; skipping run
> Oct 6 20:27:33 domU-12-31-39-0C-10-C7 puppet-agent[2500]: Could not
> send report: SSL_connect returned=1 errno=0 state=SSLv3 read server
> certificate B: certificate verify failed. This is often because the
> time is out of sync on the server or client
>
I am not entirely sure what this indicates. Can you share you puppet.conf?
>
>
> and more fun:
>
> root@domU-12-31-39-0C-10-C7:~# gem list
>
> *** LOCAL GEMS ***
>
> facter (1.6.1)
> puppet (2.7.5)
> root@domU-12-31-39-0C-10-C7:~# puppet agent
> The program 'puppet' is currently not installed. You can install it
> by typing:
> apt-get install puppet
>
This is just a side effect of puppet being installed as a gem. It is
installed, but not in the PATH:
you should be able to resolve this by updating PATH
export PATH="$PATH:/var/lib/gems/1.8/bin"
( you may want to double check this path for accuracy on your system)
>
> Am I fighting product issues? Did I do something wrong (again)?
>
> -Josh
>
> --
> 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+unsubscr...@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+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.
