puppetserver creation fails on initial docker-compose up command with error:
puppet-puppet-1 | Execution error (IllegalArgumentException) at java.net.URI/toURL (URI.java:1088).
puppet-puppet-1 | URI is not absolute
Expected Behavior
docker-compose command should start puppetserver
Steps to Reproduce
Steps to reproduce the behavior:
git clone repository
set environment variables
execute 'docker-compose up'
Environment
Main branch of pupperware as of 2021-11-22
'latest' puppetserver as defined in puppet.yml
Platform Ubuntu 20.04
The docker-compose up command succeeds in creating puppetdb and postgres containers, but the puppet server never succeeds. It exits with code 0 but generates the error below.
puppet-puppet-1 | Running /docker-entrypoint.d/55-set-masterport.sh
puppet-puppet-1 | /opt/puppetlabs/puppet/lib/ruby/vendor_gems/gems/hocon-1.3.1/lib/hocon/cli.rb:179:in `read': No such file or directory @ rb_sysopen - webserver.conf (Errno::ENOENT)
puppet-puppet-1 | from /opt/puppetlabs/puppet/lib/ruby/vendor_gems/gems/hocon-1.3.1/lib/hocon/cli.rb:179:in `get_hocon_file'
puppet-puppet-1 | from /opt/puppetlabs/puppet/lib/ruby/vendor_gems/gems/hocon-1.3.1/lib/hocon/cli.rb:111:in `main'
puppet-puppet-1 | from /opt/puppetlabs/puppet/lib/ruby/vendor_gems/gems/hocon-1.3.1/bin/hocon:4:in `<top (required)>'
puppet-puppet-1 | from /opt/puppetlabs/puppet/lib/ruby/vendor_gems/bin/hocon:23:in `load'
puppet-puppet-1 | from /opt/puppetlabs/puppet/lib/ruby/vendor_gems/bin/hocon:23:in `<main>'
puppet-puppet-1 | Running /docker-entrypoint.d/60-setup-autosign.sh
puppet-puppet-1 | Running /docker-entrypoint.d/70-set-dns-alt-names.sh
puppet-puppet-1 | Running /docker-entrypoint.d/80-ca.sh
puppet-puppet-1 | /opt/puppetlabs/puppet/lib/ruby/vendor_gems/gems/hocon-1.3.1/lib/hocon/cli.rb:179:in `read': No such file or directory @ rb_sysopen - /etc/puppetlabs/puppetserver/conf.d/ca.conf (Errno::ENOENT)
puppet-puppet-1 | from /opt/puppetlabs/puppet/lib/ruby/vendor_gems/gems/hocon-1.3.1/lib/hocon/cli.rb:179:in `get_hocon_file'
puppet-puppet-1 | from /opt/puppetlabs/puppet/lib/ruby/vendor_gems/gems/hocon-1.3.1/lib/hocon/cli.rb:111:in `main'
puppet-puppet-1 | from /opt/puppetlabs/puppet/lib/ruby/vendor_gems/gems/hocon-1.3.1/bin/hocon:4:in `<top (required)>'
puppet-puppet-1 | from /opt/puppetlabs/puppet/lib/ruby/vendor_gems/bin/hocon:23:in `load'
puppet-puppet-1 | from /opt/puppetlabs/puppet/lib/ruby/vendor_gems/bin/hocon:23:in `<main>'
puppet-puppet-1 | Running /docker-entrypoint.d/85-setup-storeconfigs.sh
puppet-puppet-1 | Running /docker-entrypoint.d/90-log-config.sh
puppet-puppet-1 | System configuration values:
puppet-puppet-1 | * HOSTNAME: 'puppet.pumahost'
puppet-puppet-1 | * hostname -f: 'puppet.pumahost'
puppet-puppet-1 | * PUPPETSERVER_HOSTNAME: 'puppet'
puppet-puppet-1 | * PUPPET_MASTERPORT: '8140'
puppet-puppet-1 | * Certname: 'puppet.pem'
puppet-puppet-1 | * DNS_ALT_NAMES: 'puppet,puppet.pumahost'
puppet-puppet-1 | * SSLDIR: '/etc/puppetlabs/puppet/ssl'
puppet-puppet-1 | CA Certificate:
puppet-puppet-1 | subject=CN = "Puppet Enterprise CA generated on puppet.pumahost at 2021-11-22 22:58:14 +0000"
puppet-puppet-1 | issuer=CN = Puppet Root CA: 8fafb38ce0dc60
puppet-puppet-1 | X509v3 extensions:
puppet-puppet-1 | X509v3 Basic Constraints: critical
puppet-puppet-1 | CA:TRUE
puppet-puppet-1 | X509v3 Key Usage: critical
puppet-puppet-1 | Certificate Sign, CRL Sign
puppet-puppet-1 | X509v3 Subject Key Identifier:
puppet-puppet-1 | D8:BA:BD:56:EC:36:AF:61:17:C6:F5:83:D9:22:64:EE:6C:98:27:86
puppet-puppet-1 | Netscape Comment:
puppet-puppet-1 | Puppet Server Internal Certificate
puppet-puppet-1 | X509v3 Authority Key Identifier:
puppet-puppet-1 | keyid:26:2A:A3:60:D7:BA:99:79:5C:5C:18:C3:8A:2B:77:A4:7E:09:58:EB
puppet-puppet-1 |
puppet-puppet-1 | Certificate puppet.pem:
puppet-puppet-1 | subject=CN = puppet
puppet-puppet-1 | issuer=CN = "Puppet Enterprise CA generated on puppet.pumahost at 2021-11-22 22:58:14 +0000"
puppet-puppet-1 | X509v3 extensions:
puppet-puppet-1 | X509v3 Basic Constraints: critical
puppet-puppet-1 | CA:FALSE
puppet-puppet-1 | Netscape Comment:
puppet-puppet-1 | Puppet Server Internal Certificate
puppet-puppet-1 | X509v3 Authority Key Identifier:
puppet-puppet-1 | keyid:D8:BA:BD:56:EC:36:AF:61:17:C6:F5:83:D9:22:64:EE:6C:98:27:86
puppet-puppet-1 |
puppet-puppet-1 | X509v3 Extended Key Usage: critical
puppet-puppet-1 | TLS Web Server Authentication, TLS Web Client Authentication
puppet-puppet-1 | X509v3 Key Usage: critical
puppet-puppet-1 | Digital Signature, Key Encipherment
puppet-puppet-1 | X509v3 Subject Key Identifier:
puppet-puppet-1 | 8F:58:E9:F8:B5:C3:DE:32:86:7E:98:52:9B:81:10:C7:E1:70:FC:9D
puppet-puppet-1 | 1.3.6.1.4.1.34380.1.3.39:
puppet-puppet-1 | ..true
puppet-puppet-1 | X509v3 Subject Alternative Name:
puppet-puppet-1 | DNS:puppet, DNS:puppet, DNS:puppet.pumahost
puppet-puppet-1 | Execution error (IllegalArgumentException) at java.net.URI/toURL (URI.java:1088).
puppet-puppet-1 | URI is not absolute
puppet-puppet-1 |
puppet-puppet-1 | Full report at:
puppet-puppet-1 | /tmp/clojure-4346921919719610333.edn
puppet-puppet-1 exited with code 0
Describe the Bug
puppetserver creation fails on initial
docker-compose upcommand with error:Expected Behavior
docker-compose command should start puppetserver
Steps to Reproduce
Steps to reproduce the behavior:
Environment
The docker-compose up command succeeds in creating puppetdb and postgres containers, but the puppet server never succeeds. It exits with code 0 but generates the error below.