Closed Xtigyro closed 4 years ago
Hi @Xtigyro , thanks for the report! There were a couple of changes in the puppetdb container that were causing issues here, but #158 should fix it! Please test it out and let me know if it works for you!
Hey @underscorgan - I'm about to test this now. Thank you - that was ultra quick! I'm gonna include a bit more changes that will go in 0.2.1
of the Helm chart.
I have a plea. We should always bump the version of the Docker images upon changes. When a certain version is released, the image should never change. Stability is very important after the setup of a particular deployment is finished, tested and validated.
@underscorgan The tests confirmed - the fix is perfect. Thank you!
Running /docker-entrypoint.d/30-configure-ssl.sh
(/ssl.sh) Using configuration values:
(/ssl.sh) * CERTNAME: 'puppetdb' (/CN=puppetdb)
(/ssl.sh) * DNS_ALT_NAMES: 'puppetdb,'
(/ssl.sh) * CA: 'https://puppet:8140/puppet-ca/v1'
(/ssl.sh) * SSLDIR: '/opt/puppetlabs/server/data/puppetdb/certs'
(/ssl.sh) * WAITFORCERT: '120' seconds
subject=CN = Puppet CA: puppet
issuer=CN = Puppet CA: puppet
Generating RSA private key, 4096 bit long modulus (2 primes)
............++++
..........................................................................++++
e is 65537 (0x010001)
writing RSA key
subject=CN = puppetdb
issuer=CN = Puppet CA: puppet
(/ssl.sh) Successfully signed certificate '/opt/puppetlabs/server/data/puppetdb/certs/certs/puppetdb.pem'
I've put my small changes into the same PR, too - https://github.com/underscorgan/pupperware/pull/1.
Wish you a good weekend!
Describe the Bug
The changes introduced 8 hours ago in
puppet/puppetdb:6.6.0
lead to an error in the third step of the post-init scripts.Logs:
Expected Behavior
In
puppet/puppetdb:6.5.0
- logs:Steps to Reproduce
Steps to reproduce the behavior:
helm install --namespace puppetserver --name puppetserver . --set puppetserver.puppeturl='https://github.com/puppetlabs/control-repo.git',puppetboard.enabled='true' --debug
Environment
Using the Helm chart.