date:20160815

Jira (PUP-6616) Acceptance: Catalog concurrency test consistently fails on Cisco XR

2016-08-15 Thread Stan Duffy (JIRA)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Stan Duffy created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-6616 
 
 
 
  Acceptance: Catalog concurrency test consistently fails on Cisco XR  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  CI Blocker 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Created:
 

 2016/08/15 8:24 PM 
 
 
 

Environment:
 
 
Puppet Agent Manual CI Pipeline 
 
 
 

Priority:
 
  Normal 
 
 
 

Reporter:
 
 Stan Duffy 
 
 
 
 
 
 
 
 
 
 
The test tests/concurrency.ticket_2659_concurrent_catalog_requests.rb fails 100% of the time on Cisco IOS XR now. At least 1 of the 5 sometimes as many as 4 of the 5 concurrent requests fail. This needs to be investigated and fixed to allow the CI to go green. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment

Jira (PUP-2018) `puppet certificate generate` Generates Two CSRs in One Run

2016-08-15 Thread Adrien Thebo (JIRA)

Title: Message Title

Adrien Thebo commented on PUP-2018

Re: `puppet certificate generate` Generates Two CSRs in One Run

Reading more information related to this ticket leads me to suspect that there might be multiple bugs that trigger this issue, but I've found at least one of them. The bug that I've found is due to how we generate a CSR the first time a HTTP connection is requested. In normal operation Puppet will request a certificate from the CA the first time that certificate is needed; in practice this is any authenticated HTTP request to the master. puppet certificate generate breaks some assumptions around this though, because that command will make requests that would normally require a certificate but when no certificate is available. If the command is used to submit a CSR for another node, then the command will actually submit a CSR and request a cert for the node itself before submitting the request for the original node. In the case where a node is requesting a certificate for itself though, Puppet will effectively submit a CSR and request a certificate so that it can then resubmit that CSR and request the same cert. This is where we get that duplicate CSR submission.

Add Comment

This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9)

--
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 (PDB-2979) puppetdb-query/db implement print-config action

2016-08-15 Thread John Duarte (JIRA)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 John Duarte created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 PuppetDB /  PDB-2979 
 
 
 
  puppetdb-query/db implement print-config action  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Affects Versions:
 

 PDB CLI 1.1.0 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Created:
 

 2016/08/15 3:27 PM 
 
 
 

Priority:
 
  Normal 
 
 
 

Reporter:
 
 John Duarte 
 
 
 
 
 
 
 
 
 
 
The puppet-code tool implements the print-config action to display the values gathered from the config file(s) in scope. For consistency, this action should be implemented in puppet-query and puppet-db. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment

Jira (PUP-6615) purge_ssh_keys parameter is not idempotent

2016-08-15 Thread Jonathan Lynch (JIRA)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Jonathan Lynch updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-6615 
 
 
 
  purge_ssh_keys parameter is not idempotent  
 
 
 
 
 
 
 
 
 

Change By:
 
 Jonathan Lynch 
 
 
 
 
 
 
 
 
 
 If you try to create a user using puppet and set purge_ssh_keys option to true, it fails unless the user already exists. For example:{ quote} {   user { 'foobar':ensure => present,managehome => true,purge_ssh_keys => true,  } {quote  } } Expected result:The user and home directory gets created if it doesn't already exist. If it does already exist, any non-managed authorized_keys get purged.Actual result:{color:red}Error: Failed to apply catalog: Parameter purge_ssh_keys failed on User[foobar]: Munging failed for value true in class purge_ssh_keys: purge_ssh_keys can only be true for users with a defined home directory {color} 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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-6615) purge_ssh_keys parameter is not idempotent

2016-08-15 Thread Jonathan Lynch (JIRA)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Jonathan Lynch updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-6615 
 
 
 
  purge_ssh_keys parameter is not idempotent  
 
 
 
 
 
 
 
 
 

Change By:
 
 Jonathan Lynch 
 
 
 
 
 
 
 
 
 
 If you try to create a user using puppet and set purge_ssh_keys option to true, it fails unless the user already exists. For example:{ { noformat}   user { 'foobar':ensure => present,managehome => true,purge_ssh_keys => true,  } {noformat } } Expected result:The user and home directory gets created if it doesn't already exist. If it does already exist, any non-managed authorized_keys get purged.Actual result:{color:red}Error: Failed to apply catalog: Parameter purge_ssh_keys failed on User[foobar]: Munging failed for value true in class purge_ssh_keys: purge_ssh_keys can only be true for users with a defined home directory {color} 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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-6615) purge_ssh_keys parameter is not idempotent

2016-08-15 Thread Jonathan Lynch (JIRA)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Jonathan Lynch created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-6615 
 
 
 
  purge_ssh_keys parameter is not idempotent  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Affects Versions:
 

 PUP 3.8.7 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Created:
 

 2016/08/15 1:00 PM 
 
 
 

Priority:
 
  Minor 
 
 
 

Reporter:
 
 Jonathan Lynch 
 
 
 
 
 
 
 
 
 
 
If you try to create a user using puppet and set purge_ssh_keys option to true, it fails unless the user already exists. For example: 

 user  

Unknown macro: { 'foobar'} 

 
Expected result: 
The user and home directory gets created if it doesn't already exist. If it does already exist, any non-managed authorized_keys get purged. 
Actual result: 
Error: Failed to apply catalog: Parameter purge_ssh_keys failed on User[foobar]: Munging failed for value true in class purge_ssh_keys: purge_ssh_keys can only be true for users with a defined home directory

Jira (PUP-6564) Support Ruby 2.3.x with Puppet 4.5.2

2016-08-15 Thread Henrik Lindberg (JIRA)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Henrik Lindberg updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-6564 
 
 
 
  Support Ruby 2.3.x with Puppet 4.5.2  
 
 
 
 
 
 
 
 
 

Change By:
 
 Henrik Lindberg 
 
 
 

Scrum Team:
 
 Client Platform 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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-6564) Support Ruby 2.3.x with Puppet 4.5.2

2016-08-15 Thread Kenn Hussey (JIRA)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Kenn Hussey updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-6564 
 
 
 
  Support Ruby 2.3.x with Puppet 4.5.2  
 
 
 
 
 
 
 
 
 

Change By:
 
 Kenn Hussey 
 
 
 

Fix Version/s:
 
 PUP 4.5.2 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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 (PDB-2960) Add --log-level flag to puppetdb-cli tool for troubleshooting

2016-08-15 Thread John Duarte (JIRA)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 John Duarte updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 PuppetDB /  PDB-2960 
 
 
 
  Add --log-level flag to puppetdb-cli tool for troubleshooting  
 
 
 
 
 
 
 
 
 

Change By:
 
 John Duarte 
 
 
 
 
 
 
 
 
 
 As a user manually configuring for puppetdb-cli tool, troubleshooting connection errors be difficult.The standard error is {code}Failed to connect to server: connection refused{code}This error occurs under at least the following circumstances:* No config file in place* Malformed config file* Missing ca file* No token presentIt would be helpful to have a {{--log-level}} flag to show the connection attempt in order to troubleshoot exactly why the connection failed.This functionality has been implemented in {{puppet-code} } for reference. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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 (PDB-2960) Add --log-level flag to puppetdb-cli tool for troubleshooting

2016-08-15 Thread John Duarte (JIRA)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 John Duarte updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 PuppetDB /  PDB-2960 
 
 
 
  Add --log-level flag to puppetdb-cli tool for troubleshooting  
 
 
 
 
 
 
 
 
 

Change By:
 
 John Duarte 
 
 
 
 
 
 
 
 
 
 As a user manually configuring for puppetdb-cli tool, troubleshooting connection errors be difficult.The standard error is {code}Failed to connect to server: connection refused{code}This error occurs under at least the following circumstances:* No config file in place* Malformed config file* Missing ca file* No token presentIt would be helpful to have a {{-- verbose log-level }}  or some other  flag to show the connection attempt in order to troubleshoot exactly why the connection failed. This functionality has been implemented in {{puppet-code} } for reference. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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 (PDB-2960) Add --verbose flag to puppetdb-cli tool for troubleshooting

2016-08-15 Thread John Duarte (JIRA)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 John Duarte commented on  PDB-2960 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Add --verbose flag to puppetdb-cli tool for troubleshooting  
 
 
 
 
 
 
 
 
 
 
This functionality has been implemented in puppet-code as --log-level, therefore I am updating this ticket to use that flag in order to make the tools consistent. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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 (PDB-2960) Add --log-level flag to puppetdb-cli tool for troubleshooting

2016-08-15 Thread John Duarte (JIRA)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 John Duarte updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 PuppetDB /  PDB-2960 
 
 
 
  Add --log-level flag to puppetdb-cli tool for troubleshooting  
 
 
 
 
 
 
 
 
 

Change By:
 
 John Duarte 
 
 
 

Summary:
 
 Add -- verbose log-level  flag to puppetdb-cli tool for troubleshooting 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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-6405) Pip package provider runs every time when updating setuptools

2016-08-15 Thread Kenn Hussey (JIRA)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Kenn Hussey commented on  PUP-6405 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Pip package provider runs every time when updating setuptools  
 
 
 
 
 
 
 
 
 
 
Kylo Ginsberg do you know if this ended up getting fixed along with 

PUP-6120
? 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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-6444) Python PIP provider version => latest stopped working for everyone pre-4.5.2

2016-08-15 Thread Kenn Hussey (JIRA)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Kenn Hussey updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-6444 
 
 
 
  Python PIP provider version => latest stopped working for everyone pre-4.5.2  
 
 
 
 
 
 
 
 
 

Change By:
 
 Kenn Hussey 
 
 
 

Fix Version/s:
 
 PUP 4.5.2 
 
 
 

Fix Version/s:
 
 PUP 4.6.0 
 
 
 

Fix Version/s:
 
 PUP 3.8.8 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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-6405) Pip package provider runs every time when updating setuptools

2016-08-15 Thread Kenn Hussey (JIRA)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Kenn Hussey updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-6405 
 
 
 
  Pip package provider runs every time when updating setuptools  
 
 
 
 
 
 
 
 
 

Change By:
 
 Kenn Hussey 
 
 
 

Fix Version/s:
 
 PUP 4.5.0 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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-6574) Function call fails when using camel case for class names. It should be handled by puppet parser syntax validator

2016-08-15 Thread Henrik Lindberg (JIRA)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Henrik Lindberg assigned an issue to Thomas Hallgren 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-6574 
 
 
 
  Function call fails when using camel case for class names. It should be handled by puppet parser syntax validator  
 
 
 
 
 
 
 
 
 

Change By:
 
 Henrik Lindberg 
 
 
 

Assignee:
 
 Henrik Lindberg Thomas Hallgren 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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-6614) Puppet 4.6.0 Error transactionstore is corrupt

2016-08-15 Thread Henrik Lindberg (JIRA)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Henrik Lindberg updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-6614 
 
 
 
  Puppet 4.6.0 Error transactionstore is corrupt  
 
 
 
 
 
 
 
 
 

Change By:
 
 Henrik Lindberg 
 
 
 

Scrum Team:
 
 Windows 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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-6614) Puppet 4.6.0 Error transactionstore is corrupt

2016-08-15 Thread Henrik Lindberg (JIRA)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Henrik Lindberg updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-6614 
 
 
 
  Puppet 4.6.0 Error transactionstore is corrupt  
 
 
 
 
 
 
 
 
 

Change By:
 
 Henrik Lindberg 
 
 
 
 
 
 
 
 
 
 With the new transaction store feature, we've encountered an issue where the transactionstore.yaml file can't be read back in.The puppet run does continue, but the red error is making my team flip out because its red and not white or yellow. ``` {code} Info: Using configured environment 'production'Info: Retrieving pluginfactsInfo: Retrieving pluginInfo: Loading factsInfo: Caching catalog for testserver.example.comError: Transaction store file C:/ProgramData/PuppetLabs/puppet/cache/state/transactionstore.yaml is corrupt (wrong number of arguments (0 for 1..2)); replacingError: Transaction state file C:/ProgramData/PuppetLabs/puppet/cache/state/transactionstore.yaml is valid YAML but not returning a hash. Check the file for corruption, or remove it before continuing.Info: Applying confiugration version '1471272929'Notice: Applied catalog in 34.12 seconds ``` {code} When i try to load the yaml with irb, it fails due to not finding `Puppet::Type::Acl` and my transactionstore.yaml contains multiple lines of `- !ruby/hash:Puppet::Type::Acl::Ace {}` on the each Acl resource at parameters/permissions/system_value location. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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

Jira (HI-512) My Organization have an a DNS Puppet and I need insert an CNAME record

2016-08-15 Thread Michelle Fredette (JIRA)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Michelle Fredette assigned an issue to Kami Olszewski 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Hiera /  HI-512 
 
 
 
  My Organization have an a DNS Puppet and I need insert an CNAME record  
 
 
 
 
 
 
 
 
 

Change By:
 
 Michelle Fredette 
 
 
 

Assignee:
 
 Kami Olszewski 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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 (HI-512) My Organization have an a DNS Puppet and I need insert an CNAME record

2016-08-15 Thread Michelle Fredette (JIRA)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Michelle Fredette updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Hiera /  HI-512 
 
 
 
  My Organization have an a DNS Puppet and I need insert an CNAME record  
 
 
 
 
 
 
 
 
 

Change By:
 
 Michelle Fredette 
 
 
 

Release Notes:
 
 Known Issue 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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 (HI-512) My Organization have an a DNS Puppet and I need insert an CNAME record

2016-08-15 Thread Michelle Fredette (JIRA)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Michelle Fredette commented on  HI-512 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: My Organization have an a DNS Puppet and I need insert an CNAME record  
 
 
 
 
 
 
 
 
 
 
Kami Olszewski - This appears to be a support issue. Can you field it? 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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-4289) user type doesn't support Full Name on Windows

2016-08-15 Thread Ethan Brown (JIRA)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Ethan Brown updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-4289 
 
 
 
  user type doesn't support Full Name on Windows  
 
 
 
 
 
 
 
 
 

Change By:
 
 Ethan Brown 
 
 
 

Fix Version/s:
 
 PUP 4.8.0 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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-6585) Remove Puppet::Util.absolute_path?(path) / replace with Pathname.new(path)

2016-08-15 Thread Ethan Brown (JIRA)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Ethan Brown updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-6585 
 
 
 
  Remove Puppet::Util.absolute_path?(path) / replace with Pathname.new(path)  
 
 
 
 
 
 
 
 
 

Change By:
 
 Ethan Brown 
 
 
 

Fix Version/s:
 
 PUP 4.7.0 
 
 
 

Fix Version/s:
 
 PUP 4.8.0 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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-2018) `puppet certificate generate` Generates Two CSRs in One Run

2016-08-15 Thread Adrien Thebo (JIRA)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Adrien Thebo assigned an issue to Adrien Thebo 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-2018 
 
 
 
  `puppet certificate generate` Generates Two CSRs in One Run  
 
 
 
 
 
 
 
 
 

Change By:
 
 Adrien Thebo 
 
 
 

Assignee:
 
 Adrien Thebo 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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-4289) user type doesn't support Full Name on Windows

2016-08-15 Thread Ethan Brown (JIRA)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Ethan Brown updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-4289 
 
 
 
  user type doesn't support Full Name on Windows  
 
 
 
 
 
 
 
 
 

Change By:
 
 Ethan Brown 
 
 
 

Fix Version/s:
 
 PUP 4.7.0 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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-6585) Remove Puppet::Util.absolute_path?(path) / replace with Pathname.new(path)

2016-08-15 Thread Kenn Hussey (JIRA)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Kenn Hussey updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-6585 
 
 
 
  Remove Puppet::Util.absolute_path?(path) / replace with Pathname.new(path)  
 
 
 
 
 
 
 
 
 

Change By:
 
 Kenn Hussey 
 
 
 

Fix Version/s:
 
 PUP 4.6.1 
 
 
 

Fix Version/s:
 
 PUP 4.7.0 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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 (PDB-2957) Fix PuppetDB CLI on Windows with Tokens

2016-08-15 Thread Susan McNerney (JIRA)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Susan McNerney commented on  PDB-2957 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Fix PuppetDB CLI on Windows with Tokens  
 
 
 
 
 
 
 
 
 
 
Windows issues weirdly seemed to resolve on Friday; AJ is spending this morning verifying the issue is really resolved.  
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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.

72 matches

Mail list logo