Jira (PDB-4540) DNS_ALT_NAMES set by docker puppetdb >= 6.6.0

2019-10-03 Thread Christoph Roeder (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Christoph Roeder updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 PuppetDB /  PDB-4540  
 
 
  DNS_ALT_NAMES set by docker puppetdb >= 6.6.0   
 

  
 
 
 
 

 
Change By: 
 Christoph Roeder  
 

  
 
 
 
 

 
 *Puppet Version: 6.7.0* *Puppet Server Version: 6.7.0* *OS Name/Version: Ubuntu 18.04*puppetdb 6.6.0 and upwards creates an dns alt cert even if no env variable DNS_ALT_NAMES is set.*Desired Behavior:* create an cert for puppetdb*Actual Behavior:* created an cert for puppetdb with alt name "puppetdb,"puppetdb_1 | Running /docker-entrypoint.d/30-configure-ssl.sh puppetdb_1 | (/ssl.sh) Using configuration values: puppetdb_1 | (/ssl.sh) * CERTNAME: 'puppetdb' (/CN=puppetdb) {color:# FF ff }puppetdb_1 | (/ssl.sh) * DNS_ALT_NAMES: 'puppetdb,' {color}puppetdb_1 | (/ssl.sh) * CA: 'https://puppet:8140/puppet-ca/v1' puppetdb_1 | (/ssl.sh) * SSLDIR: '/opt/puppetlabs/server/data/puppetdb/certs' puppetdb_1 | (/ssl.sh) * WAITFORCERT: '120' seconds puppetdb_1 | subject=CN = Puppet CA: puppet.home.roeder.io puppetdb_1 | issuer=CN = Puppet CA: puppet.home.roeder.io puppetdb_1 | (/ssl.sh) Error: CA already has signed certificate for 'puppetdb'  The Problem was introduced here [https://github.com/puppetlabs/puppetdb/commit/023bfcd0fd9e703e384e8167c768e61f22e46919]  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)  
 
 

 
   

Jira (PDB-4540) DNS_ALT_NAMES set by docker puppetdb >= 6.6.0

2019-10-03 Thread Christoph Roeder (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Christoph Roeder created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 PuppetDB /  PDB-4540  
 
 
  DNS_ALT_NAMES set by docker puppetdb >= 6.6.0   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Affects Versions: 
 PDB 6.6.0  
 
 
Assignee: 
 Unassigned  
 
 
Created: 
 2019/10/03 6:16 AM  
 
 
Fix Versions: 
 PDB 6.5.0  
 
 
Priority: 
  Major  
 
 
Reporter: 
 Christoph Roeder  
 

  
 
 
 
 

 
 Puppet Version: 6.7.0 Puppet Server Version: 6.7.0 OS Name/Version: Ubuntu 18.04 puppetdb 6.6.0 and upwards creates an dns alt cert even if no env variable DNS_ALT_NAMES is set. Desired Behavior: create an cert for puppetdb Actual Behavior: created an cert for puppetdb with alt name "puppetdb," puppetdb_1 | Running /docker-entrypoint.d/30-configure-ssl.sh  puppetdb_1 | (/ssl.sh) Using configuration values:  puppetdb_1 | (/ssl.sh) * CERTNAME: 'puppetdb' (/CN=puppetdb)  puppetdb_1 | (/ssl.sh) * DNS_ALT_NAMES: 'puppetdb,'  puppetdb_1 | (/ssl.sh) * CA: 'https://puppet:8140/puppet-ca/v1'  puppetdb_1 | (/ssl.sh) * SSLDIR: '/opt/puppetlabs/server/data/puppetdb/certs'  puppetdb_1 | (/ssl.sh) * WAITFORCERT: '120' seconds  puppetdb_1 | subject=CN = Puppet CA: puppet.home.roeder.io  puppetdb_1 | issuer=CN = Puppet CA: puppet.home.roeder.io  puppetdb_1 | (/ssl.sh) Error: CA already has signed certificate for 'puppetdb'  
 

  
 
 
 
 

 
 
 

   

Jira (PUP-6528) cron type ignores noop option

2017-05-16 Thread Christoph Roeder (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Christoph Roeder commented on  PUP-6528 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: cron type ignores noop option  
 
 
 
 
 
 
 
 
 
 
The issue was reported a year ago, so yes now it's working for me too with puppet-agent-1.10.0-1.el7.x86_64 
Thanks 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.


Jira (PUP-6528) cron type ignores noop option

2016-07-21 Thread Christoph Roeder (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Christoph Roeder created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-6528 
 
 
 
  cron type ignores noop option  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Affects Versions:
 

 PUP 4.5.2 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Created:
 

 2016/07/21 2:16 AM 
 
 
 

Priority:
 
  Normal 
 
 
 

Reporter:
 
 Christoph Roeder 
 
 
 
 
 
 
 
 
 
 
The cron type ignores the noop metaparameter. 
Example 
 
 
 
 
 
 
cron {"test": 
 
 
 
 
	command => "date", 
 
 
 
 
	user => "root", 
 
 
 
 
	hour