Ask Your Question
0

Can't create key_pair for dashboard

asked 2014-05-28 19:45:55 -0500

Pindish gravatar image

Hi,

I am setting up the latest open source Puppet 3.6.1 on Debian 7.5 using Puppet Lab package repository. I have puppetmaster, puppetdb, and puppet-dashboard all running on separate boxes.

For dashboard, I am using version 1.2.23-1puppetlabs1. Currently I have only have basic functionality set up. I want to enable the advanced features, i.e. Inventory service and file viewer. I use follow the instructions given here: http://docs.puppetlabs.com/dashboard/...

I am stuck at creating keypair. For some reason rake keeps aborting and complains about keys already exist. Every time I ran the command, it creates two files, dashboard.privatekey.pem and dashboard.public_key.pem. I deleted them and tried to run the command again, got the exact same problem:

cd /usr/share/puppet-dashboard; sudo -u www-data rake RAILSENV=production cert:createkey_pair

 ...
rake aborted!
Key(s) already exist.

Here is what the file permissions look like:

root@puppetdashboard:/usr/share/puppet-dashboard# ls -l
total 84
drwxr-xr-x  7 root     root     4096 May 24 19:04 app
drwxr-xr-x  2 root     root     4096 May 24 19:04 bin
drwxr-xr-x  2 www-data www-data 4096 May 25 00:01 certs
drwxr-xr-x  5 root     root     4096 May 24 22:42 config
drwxr-xr-x  3 root     root     4096 May 24 22:30 db
drwxr-xr-x  2 root     root     4096 May 24 19:04 examples
drwxr-xr-x  6 root     root     4096 May 24 19:04 ext
drwxr-xr-x  4 root     root     4096 May 24 19:04 lib
-rw-r--r--  1 root     root      552 Mar 21  2013 LICENSE
drwxr-xr-x  2 www-data www-data 4096 May 24 22:44 log
drwxr-xr-x  5 www-data www-data 4096 May 24 19:04 public
-rw-r--r--  1 root     root     1678 Mar 21  2013 Rakefile
-rw-r--r--  1 root     root     2795 Mar 21  2013 README.markdown
-rw-r--r--  1 root     root     2267 Mar 21  2013 README_PACKAGES.markdown
drwxr-xr-x  3 root     root     4096 May 24 19:04 script
drwxr-xr-x 10 root     root     4096 May 24 19:04 spec
drwxr-xr-x  2 www-data www-data 4096 May 27 17:43 spool
drwxr-xr-x  2 root     root     4096 May 24 19:04 templates
drwxr-xr-x  7 www-data www-data 4096 May 24 22:45 tmp
drwxr-xr-x  5 root     root     4096 May 24 19:04 vendor
-rw-r--r--  1 root     root        7 Mar 21  2013 VERSION

I use the default settings.yml:

# Node name to use when contacting the puppet master.  This is the
# CN that is used in Dashboard's certificate.
cn_name: 'dashboard'

ca_crl_path: 'certs/dashboard.ca_crl.pem'

ca_certificate_path: 'certs/dashboard.ca_cert.pem'

certificate_path: 'certs/dashboard.cert.pem'

private_key_path: 'certs/dashboard.private_key.pem'

public_key_path: 'certs/dashboard.public_key.pem'

# Hostname of the certificate authority.
ca_server: 'puppet'

# Port for the certificate authority.
ca_port: 8140

# Key length for SSL certificates
key_length: 1024

# The "inventory service" allows you to connect to a puppet master to retrieve and node facts
enable_inventory_service: false

# Hostname of the inventory server.
inventory_server: 'puppet'

# Port for the inventory server.
inventory_port: 8140

# Set this to true to allow Dashboard to display diffs on files that
# are archived in the file bucket.
use_file_bucket_diffs: false ...
(more)
edit retag flag offensive close merge delete

1 Answer

Sort by ยป oldest newest most voted
0

answered 2014-06-06 18:57:05 -0500

Pindish gravatar image

I got it working by installing puppet agent on the box and use puppet agent's certs for dashboard's settings.yml, without running the three rake commands.

edit flag offensive delete link more

Your Answer

Please start posting anonymously - your entry will be published after you log in or create a new account.

Add Answer

Question Tools

1 follower

Stats

Asked: 2014-05-28 19:45:55 -0500

Seen: 327 times

Last updated: Jun 06 '14